Main Page

<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.11/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.11/ http://www.mediawiki.org/xml/export-0.11.xsd" version="0.11" xml:lang="en">
  <siteinfo>
    <sitename>Cursed Silicons Wiki</sitename>
    <dbname>my_wiki</dbname>
    <base>https://wiki.cursedsilicon.net/wiki/Main_Page</base>
    <generator>MediaWiki 1.43.1</generator>
    <case>first-letter</case>
    <namespaces>
      <namespace key="-2" case="first-letter">Media</namespace>
      <namespace key="-1" case="first-letter">Special</namespace>
      <namespace key="0" case="first-letter" />
      <namespace key="1" case="first-letter">Talk</namespace>
      <namespace key="2" case="first-letter">User</namespace>
      <namespace key="3" case="first-letter">User talk</namespace>
      <namespace key="4" case="first-letter">Cursed Silicons Wiki</namespace>
      <namespace key="5" case="first-letter">Cursed Silicons Wiki talk</namespace>
      <namespace key="6" case="first-letter">File</namespace>
      <namespace key="7" case="first-letter">File talk</namespace>
      <namespace key="8" case="first-letter">MediaWiki</namespace>
      <namespace key="9" case="first-letter">MediaWiki talk</namespace>
      <namespace key="10" case="first-letter">Template</namespace>
      <namespace key="11" case="first-letter">Template talk</namespace>
      <namespace key="12" case="first-letter">Help</namespace>
      <namespace key="13" case="first-letter">Help talk</namespace>
      <namespace key="14" case="first-letter">Category</namespace>
      <namespace key="15" case="first-letter">Category talk</namespace>
    </namespaces>
  </siteinfo>
<page arvcontinue="">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>1</id>
    <timestamp>2024-08-31T09:24:38Z</timestamp>
    <contributor>
      <username>MediaWiki default</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="755" xml:space="preserve">&lt;strong&gt;MediaWiki has been installed.&lt;/strong&gt;

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]</text>
    <sha1>11cef88175cf81168a86e7c0327a5b2d7a1920f5</sha1>
  </revision>
  <revision>
    <id>2</id>
    <parentid>1</parentid>
    <timestamp>2024-08-31T09:32:46Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="364" xml:space="preserve">Welcome!


This is my little wiki where I'm going to keep various details about old computers and other various projects 


If you...somehow stumbled across this page on accident, perhaps you'd like to check out other places I'm more active!


'''[https://social.restless.systems/@CursedSilicon/ Mastodon]'''

'''[https://www.youtube.com/@CursedSilicon YouTube]'''</text>
    <sha1>489b82b1ffe3c1913e779f87e650fe1c8f5d3979</sha1>
  </revision>
  <revision>
    <id>11</id>
    <parentid>2</parentid>
    <timestamp>2024-08-31T10:07:07Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="515" xml:space="preserve">Welcome!


This is my little wiki where I'm going to keep various details about old computers and other various projects  

For now [[Old Computers|here's a page of my old computers]]. I'm constantly expanding the list and documenting everything I can about them 


If you...somehow stumbled across this page on accident however, perhaps you'd like to check out other places I'm more active!


'''[https://social.restless.systems/@CursedSilicon/ Mastodon]'''

'''[https://www.youtube.com/@CursedSilicon YouTube]'''</text>
    <sha1>70883294ab374a6cc6a24f198f44bac9c7b9460e</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Old Computers</title>
  <ns>0</ns>
  <id>2</id>
  <revision>
    <id>3</id>
    <timestamp>2024-08-31T09:34:32Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "As the title suggests, and indeed why you're here. '''''I have a lot of old computers'''''  This page serves as an index catalog of them for easy reference"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="155" xml:space="preserve">As the title suggests, and indeed why you're here. '''''I have a lot of old computers'''''

This page serves as an index catalog of them for easy reference</text>
    <sha1>357433d13da069451659f8091df0e1714fa42b3a</sha1>
  </revision>
  <revision>
    <id>12</id>
    <parentid>3</parentid>
    <timestamp>2024-08-31T10:08:14Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="212" xml:space="preserve">As the title suggests, and indeed why you're here. '''''I have a lot of old computers'''''

This page serves as an index catalog of them for easy reference

=== Cobalt Networks ===
[[Cobalt Qube]]

[[Cobalt RaQ]]</text>
    <sha1>fae23fc63c048ecbba49a3ffd8b3d5eb239ec5c0</sha1>
  </revision>
  <revision>
    <id>17</id>
    <parentid>12</parentid>
    <timestamp>2024-08-31T10:31:28Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="251" xml:space="preserve">As the title suggests, and indeed why you're here. '''''I have a lot of old computers'''''

This page serves as an index catalog of them for easy reference

=== Cobalt Networks ===
[[Cobalt Qube]]

[[Cobalt RaQ]]

=== Sun Microsystems ===
[[Netra X1]]</text>
    <sha1>8c890807d7a06ef4124d9426abf55fda198061cc</sha1>
  </revision>
  <revision>
    <id>18</id>
    <parentid>17</parentid>
    <timestamp>2024-08-31T10:53:53Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="965" xml:space="preserve">As the title suggests, and indeed why you're here. '''''I have a lot of old computers'''''

This page serves as an index catalog of them for easy reference.

== '''NOTE: This list is non-exhaustive as I'm constantly picking up new weird old tech''' ==


=== Acer Inc ===
[[Acer EasyStore H340|Acer EasyStore H340 NAS]]

=== Apple Computers, Inc ===
[[Powermac G4]] "Mirror Drive Door" (MDD)

[[Powermac G5]] Quad

[[eMac G4]]

[[Xserve G4]]

[[Xserve G5]]


=== Cobalt Networks ===
[[Cobalt Qube]]

[[Cobalt RaQ]]

=== Digital Equipment Corporation ===
[[DEC AlphaServer 2100|DEC AlphaServer 2100 4/275]]

=== Hewlett Packard ===
[[HP MediaSmart EX495]]

=== Sun Microsystems ===
[[Netra X1]]

[[Netra T1]]

[[SunFire Enterprise 420R]] 

[[Ultra 10 Workstation]]

=== Whitebox/custom builds ===


[[Worlds Fastest Win98 PC]]

[[Disc Ripper|Disc Ripper aka "Napster"]]

=== Miscellaneous (Anything not 'retro') ===
[[Framework 13]]

[[Main Desktop]]

[[Home Server]]</text>
    <sha1>e1ac06e43baf0b7114c820dee206ffdb466d6795</sha1>
  </revision>
  <revision>
    <id>19</id>
    <parentid>18</parentid>
    <timestamp>2024-08-31T10:54:11Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="963" xml:space="preserve">As the title suggests, and indeed why you're here. '''''I have a lot of old computers'''''

This page serves as an index catalog of them for easy reference.

= '''NOTE: This list is non-exhaustive as I'm constantly picking up new weird old tech''' =


=== Acer Inc ===
[[Acer EasyStore H340|Acer EasyStore H340 NAS]]

=== Apple Computers, Inc ===
[[Powermac G4]] "Mirror Drive Door" (MDD)

[[Powermac G5]] Quad

[[eMac G4]]

[[Xserve G4]]

[[Xserve G5]]


=== Cobalt Networks ===
[[Cobalt Qube]]

[[Cobalt RaQ]]

=== Digital Equipment Corporation ===
[[DEC AlphaServer 2100|DEC AlphaServer 2100 4/275]]

=== Hewlett Packard ===
[[HP MediaSmart EX495]]

=== Sun Microsystems ===
[[Netra X1]]

[[Netra T1]]

[[SunFire Enterprise 420R]] 

[[Ultra 10 Workstation]]

=== Whitebox/custom builds ===


[[Worlds Fastest Win98 PC]]

[[Disc Ripper|Disc Ripper aka "Napster"]]

=== Miscellaneous (Anything not 'retro') ===
[[Framework 13]]

[[Main Desktop]]

[[Home Server]]</text>
    <sha1>95548b9d2684725be9a343d487224dc5e333f8bb</sha1>
  </revision>
  <revision>
    <id>20</id>
    <parentid>19</parentid>
    <timestamp>2024-08-31T10:54:47Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="970" xml:space="preserve">As the title suggests, and indeed why you're here. '''''I have a lot of old computers'''''

This page serves as an index catalog of them for easy reference.

&lt;big&gt;'''NOTE: This list is non-exhaustive as I'm constantly picking up new weird old tech'''&lt;/big&gt;


=== Acer Inc ===
[[Acer EasyStore H340|Acer EasyStore H340 NAS]]

=== Apple Computers, Inc ===
[[Powermac G4]] "Mirror Drive Door" (MDD)

[[Powermac G5]] Quad

[[eMac G4]]

[[Xserve G4]]

[[Xserve G5]]


=== Cobalt Networks ===
[[Cobalt Qube]]

[[Cobalt RaQ]]

=== Digital Equipment Corporation ===
[[DEC AlphaServer 2100|DEC AlphaServer 2100 4/275]]

=== Hewlett Packard ===
[[HP MediaSmart EX495]]

=== Sun Microsystems ===
[[Netra X1]]

[[Netra T1]]

[[SunFire Enterprise 420R]] 

[[Ultra 10 Workstation]]

=== Whitebox/custom builds ===


[[Worlds Fastest Win98 PC]]

[[Disc Ripper|Disc Ripper aka "Napster"]]

=== Miscellaneous (Anything not 'retro') ===
[[Framework 13]]

[[Main Desktop]]

[[Home Server]]</text>
    <sha1>30003a27d4bc6b7593ff40c2956bff67b04d2c3b</sha1>
  </revision>
  <revision>
    <id>21</id>
    <parentid>20</parentid>
    <timestamp>2024-09-01T00:54:08Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1002" xml:space="preserve">As the title suggests, and indeed why you're here. '''''I have a lot of old computers'''''

This page serves as an index catalog of them for easy reference.

&lt;big&gt;'''NOTE: This list is non-exhaustive as I'm constantly picking up new weird old tech'''&lt;/big&gt;


=== Acer Inc ===
[[Acer EasyStore H340|Acer EasyStore H340 NAS]]

=== Apple Computers, Inc ===
[[Powermac G4]] "Mirror Drive Door" (MDD)

[[Powermac G5]] Quad

[[eMac G4]]

[[Xserve G4]]

[[Xserve G5]]


=== Cobalt Networks ===
[[Cobalt Qube]]

[[Cobalt RaQ]]

=== Digital Equipment Corporation ===
[[DEC AlphaServer 2100|DEC AlphaServer 2100 4/275]]

=== Hewlett Packard ===
[[HP MediaSmart EX495]]

=== Sun Microsystems ===
[[Netra X1]]

[[Netra T1]]

[[SunFire Enterprise 420R]] 

[[Ultra 10 Workstation]]

=== Whitebox/custom builds ===


[[Worlds Fastest Win98 PC]]

[[Disc Ripper|Disc Ripper aka "Napster"]]

=== Miscellaneous (Anything not 'retro') ===
[[Framework 13]]

[[Main Desktop]]

[[Home Server]]

[[Hyve Zeus]]

[[Hyve Cygnus]]</text>
    <sha1>9ca54b57dce0b3ed75178fa47c82dddc0e874067</sha1>
  </revision>
  <revision>
    <id>23</id>
    <parentid>21</parentid>
    <timestamp>2024-09-02T10:09:51Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1197" xml:space="preserve">As the title suggests, and indeed why you're here. '''''I have a lot of old computers'''''

This page serves as an index catalog of them for easy reference.

&lt;big&gt;'''NOTE: This list is non-exhaustive as I'm constantly picking up new weird old tech'''&lt;/big&gt;


=== Acer Inc ===
[[Acer EasyStore H340]]

=== Apple Computers Inc ===
[[Powermac G4]] "Mirror Drive Door" (MDD)

[[Powermac G5]] Quad

[[eMac G4]]

[[Xserve G4]]

[[Xserve G5]]
=== Cobalt Networks ===
[[Cobalt Qube]]

[[Cobalt RaQ|Cobalt RaQ4]]

=== Dell Computers ===
[[PowerEdge 2500]]

=== Digital Equipment Corporation ===
[[DEC AlphaServer 2100|DEC AlphaServer 2100 4/275]]

=== Hewlett Packard ===
[[HP MediaSmart EX495]]

[[HP KAYAK XA 6/400 MT]]

=== Silicon Graphics ===
[[SGI Octane]]

[[SGI Visual Workstation 320]]

=== Sun Microsystems ===
[[Netra X1]]

[[Netra T1]]

[[SunFire Enterprise 420R]] 

[[Ultra 10 Workstation]]

[[Unknown Sun Equipment]]

=== Whitebox/custom builds ===

[[Windows 98 PC|World's Fastest Windows 98 PC]]

[[Disc Ripper|Disc Ripper aka "Napster"]]

=== Miscellaneous (Anything not 'retro') ===
[[Framework 13]]

[[Main Desktop]]

[[Home Server]]

[[Hyve Zeus]]

[[Hyve Cygnus]]

[[Video Capture PC]]</text>
    <sha1>db83e91e25b23049625d69ada19c62bd030605cb</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Cobalt Qube</title>
  <ns>0</ns>
  <id>3</id>
  <revision>
    <id>4</id>
    <timestamp>2024-08-31T09:35:52Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Actually I have *two* Cobalt Qubes. Which one are you interested in?  Cobalt Qube 2 (MIPS)  Cobalt Qube 3 (AMD K6, x86)"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="119" xml:space="preserve">Actually I have *two* Cobalt Qubes. Which one are you interested in?

Cobalt Qube 2 (MIPS)

Cobalt Qube 3 (AMD K6, x86)</text>
    <sha1>270d0329ba58d644bbc467df5e1d27ccc55dd8fb</sha1>
  </revision>
  <revision>
    <id>5</id>
    <parentid>4</parentid>
    <timestamp>2024-08-31T09:36:23Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="127" xml:space="preserve">Actually I have '''''two''''' Cobalt Qubes. Which one are you interested in?

Cobalt Qube 2 (MIPS)

Cobalt Qube 3 (AMD K6, x86)</text>
    <sha1>a80c553d923dd5db2a8f118606d5797d9ee9877d</sha1>
  </revision>
  <revision>
    <id>9</id>
    <parentid>5</parentid>
    <timestamp>2024-08-31T10:00:12Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="131" xml:space="preserve">Actually I have '''''two''''' Cobalt Qubes. Which one are you interested in?

[[Cobalt Qube 2]] (MIPS)

Cobalt Qube 3 (AMD K6, x86)</text>
    <sha1>c48ce44286a5eb73331cd70eaae72980c30c1ca9</sha1>
  </revision>
  <revision>
    <id>13</id>
    <parentid>9</parentid>
    <timestamp>2024-08-31T10:08:32Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="135" xml:space="preserve">Actually I have '''''two''''' Cobalt Qubes. Which one are you interested in?

[[Cobalt Qube 2]] (MIPS)

[[Cobalt Qube 3]] (AMD K6, x86)</text>
    <sha1>d743f159f5ab5f1a9b600f464e00a5ed2b010d4b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Cobalt Qube 2</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>6</id>
    <timestamp>2024-08-31T09:56:02Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The Cobalt Qube was a computer server appliance product line, meant to be web servers, developed by Cobalt Networks, Inc. (later purchased by Sun Microsystems) from 1998 to 2002 featuring a modified Red Hat Linux operating system and a proprietary Web GUI for server management.   The original Qube systems were equipped with MIPS RM5230 (150Mhz, Original Qube) or RM5231 (250Mhz, Qube 2) processors.   Both models come with 16MB of RAM (2x8MB SIMM's) and an 8GB or 10GB 3.5..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1976" xml:space="preserve">The Cobalt Qube was a computer server appliance product line, meant to be web servers, developed by Cobalt Networks, Inc. (later purchased by Sun Microsystems) from 1998 to 2002 featuring a modified Red Hat Linux operating system and a proprietary Web GUI for server management. 

The original Qube systems were equipped with MIPS RM5230 (150Mhz, Original Qube) or RM5231 (250Mhz, Qube 2) processors. 

Both models come with 16MB of RAM (2x8MB SIMM's) and an 8GB or 10GB 3.5 inch IDE hard disk as standard.

Gateway also produced re-badged Cobalt Qube 2's which came in black and included a PCI Dial-Up modem. I do not have one of these so I cannot document its functionality or specifications

The original power supply can (and should) be replaced with a 45W USB-C power adapter. Bridging it requires a USB-C to 12V barrel connector and a Barrel to 3-pin DIN (Male) 5.5x 2.1mm cable

There is also a 40mm internal fan that should be replaced. Installing heatsinks on all internal chips is also recommended to prolong the lifespan of the device.


My Cobalt Qube 2 has been significantly modified since I purchased it from a user on eBay in late 2023. Some of the present modifications include

- RAM is maxed out to 256MB

- The original IDE hard disk has been replaced with 120GB SATA SSD using Startech SATA to IDE adapter. Due to the slow disk controller on the Cobalt Qube 2 (4MB/s at best) an SD card may be a more economical replacement 

- The "BIOS" (or system bootstrap ROM) has been replaced with the "CoLo" bootloader. The original Cobalt firmware was hard-coded to launch a Linux kernel from an '''ext2 ''(not ext3 or ext4!)''''' partition on /dev/hda1


CoLo additionally allows connection to the unit via the RS232 serial port for system control after power on. The standard 115200,8,1 configuration will allow connection to the unit. Kernels can be downloaded and executed via TFTP via the CoLo interface


At this time the unit is not presently in operation</text>
    <sha1>34756d7be3407bab83a99e47272307e9f9d24b66</sha1>
  </revision>
  <revision>
    <id>7</id>
    <parentid>6</parentid>
    <timestamp>2024-08-31T09:57:08Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1997" xml:space="preserve">The Cobalt Qube was a computer server appliance product line, meant to be web servers, developed by Cobalt Networks, Inc. (later purchased by Sun Microsystems) from 1998 to 2002 featuring a modified Red Hat Linux operating system and a proprietary Web GUI for server management. 

The original Qube systems were equipped with MIPS RM5230 (150Mhz, Original Qube) or RM5231 (250Mhz, Qube 2) processors. 

Both models come with 16MB of RAM (2x8MB SIMM's) and an 8GB or 10GB 3.5 inch IDE hard disk as standard.

Gateway also produced re-badged Cobalt Qube 2's which came in black and included a PCI Dial-Up modem. I do not have one of these so I cannot document its functionality or specifications

The original power supply can (and should) be replaced with a 45W USB-C power adapter. Bridging it requires a USB-C to 12V barrel connector and a Barrel to 3-pin DIN (Male) 5.5x 2.1mm cable

There is also a 40mm internal fan that should be replaced. Installing heatsinks on all internal chips is also recommended to prolong the lifespan of the device.


My Cobalt Qube 2 has been significantly modified since I purchased it from a user on eBay in late 2023. Some of the present modifications include

* RAM is maxed out to 256MB

* The original IDE hard disk has been replaced with 120GB SATA SSD using Startech SATA to IDE adapter. Due to the slow disk controller on the Cobalt Qube 2 (4MB/s at best) an SD card may be a more economical replacement
* The "BIOS" (or system bootstrap ROM) has been replaced with the "CoLo" bootloader. The original Cobalt firmware was hard-coded to launch a Linux kernel from an '''ext2 ''(not ext3 or ext4!)''''' partition on /dev/hda1


CoLo additionally allows connection to the unit via the RS232 serial port for system control after power on. The standard 115200,8,1 configuration will allow connection to the unit. Kernels can be downloaded and executed via TFTP via the CoLo interface


'''At this time the unit is functional, but not presently in operation'''</text>
    <sha1>6b011fc5e7fd25abaf84252f2bd9c68b074a855b</sha1>
  </revision>
  <revision>
    <id>8</id>
    <parentid>7</parentid>
    <timestamp>2024-08-31T09:59:01Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2071" xml:space="preserve">The Cobalt Qube was the worlds first "Linux Appliance" designed and released by Cobalt Networks (later purchased by Sun Microsystems). Sold from 1998 to 2002 it features a modified Red Hat Linux operating system and a proprietary Web GUI for server management. 

The original Qube systems were equipped with MIPS RM5230 (150Mhz, Original Qube) or RM5231 (250Mhz, Qube 2) processors. These CPU's are similar to the RM5000 series in Sun's "Indy" workstations. 

Both the Qube 1 and 2 come with 16MB of RAM (2x8MB SIMM's) and an 8GB or 10GB 3.5 inch IDE hard disk as standard. 

Gateway also produced re-badged Cobalt Qube 2's which came in black and included a PCI Dial-Up modem. '''I do not have one of these so I cannot document its functionality or specifications'''

The original power supply can (and should) be replaced with a 45W USB-C power adapter. Bridging it requires a USB-C to 12V barrel connector and a Barrel to 3-pin DIN (Male) 5.5x 2.1mm cable

There is also a 40mm internal fan that should be replaced. Installing heatsinks on all internal chips is also recommended to prolong the lifespan of the device.


My Cobalt Qube 2 has been significantly modified since I purchased it from a user on eBay in late 2023. Some of the present modifications include

* RAM is maxed out to 256MB

* The original IDE hard disk has been replaced with 120GB SATA SSD using Startech SATA to IDE adapter. Due to the slow disk controller on the Cobalt Qube 2 (4MB/s at best) an SD card may be a more economical replacement
* The "BIOS" (or system bootstrap ROM) has been replaced with the "CoLo" bootloader. The original Cobalt firmware was hard-coded to launch a Linux kernel from an '''ext2 ''(not ext3 or ext4!)''''' partition on /dev/hda1


CoLo additionally allows connection to the unit via the RS232 serial port for system control after power on. The standard 115200,8,1 configuration will allow connection to the unit. Kernels can be downloaded and executed via TFTP via the CoLo interface


'''At this time the unit is functional, but not presently in operation'''</text>
    <sha1>927f59443872e976049b280a0e5688362dff4a1e</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Cobalt Qube 3</title>
  <ns>0</ns>
  <id>5</id>
  <revision>
    <id>10</id>
    <timestamp>2024-08-31T10:06:03Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The Cobalt Qube 3 was the final Cobalt Qube product, released in 2002. Cobalt Networks (acquired shortly after by Sun Microsystems) discontinued it shortly after to focus on the Cobalt "RaQ" line of 1U server appliances instead    The Qube 3 is a large departure from the older Cobalt Qube 2. Moving to an AMD K-6 2 at either 300 or 450Mhz and including a SCSI and USB port on the rear of the unit.    The power connector was also re-designed to a 5 pin DIN connector requiri..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="836" xml:space="preserve">The Cobalt Qube 3 was the final Cobalt Qube product, released in 2002. Cobalt Networks (acquired shortly after by Sun Microsystems) discontinued it shortly after to focus on the Cobalt "RaQ" line of 1U server appliances instead 


The Qube 3 is a large departure from the older Cobalt Qube 2. Moving to an AMD K-6 2 at either 300 or 450Mhz and including a SCSI and USB port on the rear of the unit. 


The power connector was also re-designed to a 5 pin DIN connector requiring multiple ATX PC style voltages. Specifically +12V @ 2.0A, -12V @ 0.5A and +5V at 6.0A


'''Cobalt Qube 3's unfortunately suffer from capacitor plague and should be immediately inspected and have all of their capacitors replaced to ensure continued operation'''


'''At this time my Cobalt Qube 3 is non-operational due to lacking a compatible power supply'''</text>
    <sha1>279ecdecab1521f99dd908624aed79bfee9cb3dd</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Netra X1</title>
  <ns>0</ns>
  <id>6</id>
  <revision>
    <id>14</id>
    <timestamp>2024-08-31T10:23:07Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "For some terrible reason I picked up a bunch (five) Sun Netra X1's a couple years ago during a visit to Re-PC  Unfortunately these machines are '''terrible''' for a multitude of reasons!  Unlike their "Netra T1" counterparts the X1's were built to be as cheap as possible.   Netra X1's all come with either a 400Mhz or 500Mhz UltraSPARC IIe CPU.   400Mhz models can accept a maximum of 1GB of PC133 RAM, 500Mhz models can accept 2GB  All models come equipped with dual 10/100..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="784" xml:space="preserve">For some terrible reason I picked up a bunch (five) Sun Netra X1's a couple years ago during a visit to Re-PC

Unfortunately these machines are '''terrible''' for a multitude of reasons!

Unlike their "Netra T1" counterparts the X1's were built to be as cheap as possible.


Netra X1's all come with either a 400Mhz or 500Mhz UltraSPARC IIe CPU. 

400Mhz models can accept a maximum of 1GB of PC133 RAM, 500Mhz models can accept 2GB

All models come equipped with dual 10/100 "DEC Tulip" ethernet ports and up to two 40GB IDE hard disks, with proprietary mounts 

Like all Sun machines the servers require an RJ45-to-RS232 cable connected in order to access OpenFirmware.


With that out of the way here's some of the many problems you as a Sun Netra X1 owner can expect to encounter</text>
    <sha1>d47b79cae496a59803bce35f9b1d2f7e9526676d</sha1>
  </revision>
  <revision>
    <id>15</id>
    <parentid>14</parentid>
    <timestamp>2024-08-31T10:27:53Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1933" xml:space="preserve">For some terrible reason I picked up a bunch (five) Sun Netra X1's a couple years ago during a visit to Re-PC

Unfortunately these machines are '''terrible''' for a multitude of reasons!

Unlike their "Netra T1" counterparts the X1's were built to be as cheap as possible.


Netra X1's all come with either a 400Mhz or 500Mhz UltraSPARC IIe CPU. 

400Mhz models can accept a maximum of 1GB of PC133 RAM, 500Mhz models can accept 2GB

All models come equipped with dual 10/100 "DEC Tulip" ethernet ports and up to two 40GB IDE hard disks, with proprietary mounts 

Like all Sun machines the servers require an RJ45-to-RS232 cable connected in order to access OpenFirmware.


== Here's some of the many problems you as a Sun Netra X1 owner can expect to encounter ==

* Bad capacitors! These machines were built to be as cheap as possible. As such the capacitors will probably have already leaked, or are very excited to do so. Make sure you replace them!

* Extremely flaky ALi controller. Sun decided that in order to meet cost they would simply use as many "x86 parts" as possible. The chipset in use is from the notoriously bad ALi and will give you no end of annoying problems 

* Large hard disks won't work. Anything over 120GB seems to make the ALi controller just fall over dead

* Memory: You need to find PC133 ECC RAM. Good luck, that stuff is expensive. And the 4 slots are angled in such a way as to make it incredibly annoying to install or remove that RAM!

* The ethernet chips are rated for "10/100 operation", but due to the crappy ALi controller and a lack of DMA, iperf tests seem to cap out at around 2MB/s while pinning the poor CPU at 100% utilization

* Linux support is non-existent! The bad ALi controller seems to reset itself on boot under Linux which causes the IDE hard disks to simply...disappear! Rendering the root filesystem inaccessible 

* OpenBSD works but is extremely slow. Your milage may vary</text>
    <sha1>796ffa07a8274f047e624565d1ce822bfdd5bd1d</sha1>
  </revision>
  <revision>
    <id>16</id>
    <parentid>15</parentid>
    <timestamp>2024-08-31T10:30:00Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2069" xml:space="preserve">For some terrible reason I picked up a bunch (five) Sun Netra X1's a couple years ago during a visit to Re-PC

Unfortunately these machines are '''terrible''' for a multitude of reasons!

Unlike their "Netra T1" counterparts the X1's were built to be as cheap as possible.


Netra X1's all come with either a 400Mhz or 500Mhz UltraSPARC IIe CPU. 

400Mhz models can accept a maximum of 1GB of PC133 RAM, 500Mhz models can accept 2GB

All models come equipped with dual 10/100 "DEC Tulip" ethernet ports and up to two 40GB IDE hard disks, with proprietary mounts 

Like all Sun machines the servers require an RJ45-to-RS232 cable connected in order to access OpenFirmware.


== Here's some of the many problems you as a Sun Netra X1 owner can expect to encounter ==

* Bad capacitors! These machines were built to be as cheap as possible. As such the capacitors will probably have already leaked, or are very excited to do so. Make sure you replace them!

* Extremely flaky ALi controller. Sun decided that in order to meet cost they would simply use as many "x86 parts" as possible. The chipset in use is from the notoriously bad ALi and will give you no end of annoying problems 

* Large hard disks won't work. Anything over 120GB seems to make the ALi controller just fall over dead

* Memory: You need to find PC133 ECC RAM. Good luck, that stuff is expensive. And the 4 slots are angled in such a way as to make it incredibly annoying to install or remove that RAM!

* The ethernet chips are rated for "10/100 operation", but due to the crappy ALi controller and a lack of DMA, iperf tests seem to cap out at around 2MB/s while pinning the poor CPU at 100% utilization

* Linux support is non-existent! The bad ALi controller seems to reset itself on boot under Linux which causes the IDE hard disks to simply...disappear! Rendering the root filesystem inaccessible 

* OpenBSD works but is extremely slow. Your milage may vary


'''Unsurprisingly with all of the above issues my Netra X1's are not in use, and are unlikely to be used in the foreseeable future'''</text>
    <sha1>2af58ccbf18205a76ae40517310eb34ad42ce6cd</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Hyve Zeus</title>
  <ns>0</ns>
  <id>7</id>
  <revision>
    <id>22</id>
    <timestamp>2024-09-01T00:58:09Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The Hyve "Zeus" is a server made for Facebook before their "Open Compute Project". As a result there's about a bajillion of these things floating around on eBay these days   Hyve Zeus units feature a Super Micro X9DRD-iF motherboard with all PCI-E slots except for one removed   They are usually equipped with some variation of low-end Intel Xeons with passively cooled heatsinks attached   The unit I (unfortunately) upgraded with two top-end Xeon 2697v2's and 128GB of DDR3..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="792" xml:space="preserve">The Hyve "Zeus" is a server made for Facebook before their "Open Compute Project". As a result there's about a bajillion of these things floating around on eBay these days


Hyve Zeus units feature a Super Micro X9DRD-iF motherboard with all PCI-E slots except for one removed


They are usually equipped with some variation of low-end Intel Xeons with passively cooled heatsinks attached


The unit I (unfortunately) upgraded with two top-end Xeon 2697v2's and 128GB of DDR3 ECC memory. As a result the unit now contains two 30,000 RPM copper heatsink + fan units from Delta. The resulting noise of this server renders it virtually unusable in areas with people present 


'''It is presently part of the infrastructure of my local hackerspace. However we are likely to retire it in future'''</text>
    <sha1>fe168435f4b12fefd3c7e91ffbba22932d123156</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Acer EasyStore H340</title>
  <ns>0</ns>
  <id>8</id>
  <revision>
    <id>24</id>
    <timestamp>2024-09-02T10:24:30Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The Acer EasyStore H340 was a home NAS sold by Acer during the Windows Home Server era. Much like its "cousin" the [[HP MediaSmart EX495]] it came pre-loaded with [[Windows Home Server 2007]]  By default this device would come with 4x 1TB SATA 3.5" hard disks installed. The top most drive includes a warning label explaining that the operating system is installed on it and to be careful with removing or replacing the drive.  The machine originally shipped with an extremel..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1579" xml:space="preserve">The Acer EasyStore H340 was a home NAS sold by Acer during the Windows Home Server era. Much like its "cousin" the [[HP MediaSmart EX495]] it came pre-loaded with [[Windows Home Server 2007]]

By default this device would come with 4x 1TB SATA 3.5" hard disks installed. The top most drive includes a warning label explaining that the operating system is installed on it and to be careful with removing or replacing the drive.

The machine originally shipped with an extremely anemic Intel Atom 230 CPU and 2GB of DDR2 memory as standard to compliment the storage. It also contains a single PCI-E slot for (small!) expansion cards.

Unfortunately my H340 suffered significant damage in shipping as the device was *extremely* poorly packaged. As a result the internals of the machine have been completely replaced.

At this time the machine has an ASUS AT4NM10T ITX motherboard installed. This board features an Atom D525 chip and can support up to 8GB of SODIMM (laptop) memory. This chip is roughly comparable to two Atom 230's "glued" together and is extremely unreliable in operation. Despite having 4 SATA ports, only two ports operate at SATA 3 (6Gbps) speeds, the other two are SATA 2 (3Gbps) ports. Ethernet is handled by an onboard gigabit Realtek chip as standard 

During a stream in 2023 I was able to get this machine to run [[Windows Server 2000|'''''Windows Server 2000''''']] successfully. This proved quite stable and extremely performant over the newer Server 2003 R2 x64. This unit may be repurposed in future to run services atop that operating system version.</text>
    <sha1>a6c90b980e983e8227a2a3570ba0ec8e47b2369d</sha1>
  </revision>
  <revision>
    <id>27</id>
    <parentid>24</parentid>
    <timestamp>2024-09-02T10:33:49Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1735" xml:space="preserve">The Acer EasyStore H340 was a home NAS sold by Acer during the Windows Home Server era. Much like its "cousin" the [[HP MediaSmart EX495]] it came pre-loaded with [[Windows Home Server 2007]]


By default this device would come with 4x 1TB SATA 3.5" hard disks installed. The top most drive includes a warning label explaining that the operating system is installed on it and to be careful with removing or replacing the drive.

The machine originally shipped with an extremely anemic Intel Atom 230 CPU and 2GB of DDR2 memory as standard to compliment the storage. It also contains a single PCI-E slot for (small!) expansion cards.

Unfortunately my H340 suffered significant damage in shipping as the device was *extremely* poorly packaged. As a result the internals of the machine have been completely replaced.

At this time the machine has an ASUS AT4NM10T ITX motherboard installed. This board features an Atom D525 chip and can support up to 8GB of SODIMM (laptop) memory. This chip is roughly comparable to two Atom 230's "glued" together and is extremely unreliable in operation. Despite having 4 SATA ports, only two ports operate at SATA 3 (6Gbps) speeds, the other two are SATA 2 (3Gbps) ports. Ethernet is handled by an onboard gigabit Realtek chip as standard 

During a stream in 2023 I was able to get this machine to run [[Windows Server 2000|'''''Windows Server 2000''''']] successfully. This proved quite stable and extremely performant over the newer Server 2003 R2 x64. This unit may be repurposed in future to run services atop that operating system version.
[[File:Acer EasyStore Front.jpg|none|thumb|Front view of Acer EasyStore]]
[[File:Rear view of EasyStore.jpg|none|thumb|Rear view of Acer EasyStore H340]]</text>
    <sha1>4efd5f3d8dab243929fb1576ea13ebc4a1215cad</sha1>
  </revision>
  <revision>
    <id>28</id>
    <parentid>27</parentid>
    <timestamp>2024-09-02T10:38:54Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1737" xml:space="preserve">The Acer EasyStore H340 was a home NAS sold by Acer during the Windows Home Server era. Much like its "cousin" the [[HP MediaSmart EX495]] it came pre-loaded with [[Windows Home Server 2007]]


By default this device would come with 4x 1TB SATA 3.5" hard disks installed. The top most drive includes a warning label explaining that the operating system is installed on it and to be careful with removing or replacing the drive.

The machine originally shipped with an extremely anemic Intel Atom 230 CPU and 2GB of DDR2 memory as standard to compliment the storage. It also contains a single PCI-E slot for (small!) expansion cards.

Unfortunately my H340 suffered significant damage in shipping as the device was *extremely* poorly packaged. As a result the internals of the machine have been completely replaced.

At this time the machine has an ASUS AT4NM10T-I ITX motherboard installed. This board features an Atom D525 chip and can support up to 8GB of SODIMM (laptop) memory. This chip is roughly comparable to two Atom 230's "glued" together and is extremely unreliable in operation. Despite having 4 SATA ports, only two ports operate at SATA 3 (6Gbps) speeds, the other two are SATA 2 (3Gbps) ports. Ethernet is handled by an onboard gigabit Realtek chip as standard 

During a stream in 2023 I was able to get this machine to run [[Windows Server 2000|'''''Windows Server 2000''''']] successfully. This proved quite stable and extremely performant over the newer Server 2003 R2 x64. This unit may be repurposed in future to run services atop that operating system version.
[[File:Acer EasyStore Front.jpg|none|thumb|Front view of Acer EasyStore]]
[[File:Rear view of EasyStore.jpg|none|thumb|Rear view of Acer EasyStore H340]]</text>
    <sha1>2f737f731884bde15267e2e0f15c8af50005868f</sha1>
  </revision>
  <revision>
    <id>29</id>
    <parentid>28</parentid>
    <timestamp>2024-09-02T10:52:50Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1583" xml:space="preserve">The Acer EasyStore H340 was a home NAS sold by Acer during the Windows Home Server era. Much like its "cousin" the [[HP MediaSmart EX495]] it came pre-loaded with [[Windows Home Server 2007]]


By default this device would come with 4x 1TB SATA 3.5" hard disks installed. The top most drive includes a warning label explaining that the operating system is installed on it and to be careful with removing or replacing the drive.

The machine originally shipped with an extremely anemic Intel Atom 230 CPU and 2GB of DDR2 memory as standard to compliment the storage. It also contains a single PCI-E slot for (small!) expansion cards.

Unfortunately my H340 suffered significant damage in shipping as the device was *extremely* poorly packaged. As a result the internals of the machine have been completely replaced.

At this time the machine has an ASUS AT4NM10T-I ITX motherboard installed. This board features an Atom D525 chip and can support up to 8GB of SODIMM (laptop) memory. This chip is roughly comparable to two Atom 230's "glued" together and is extremely unreliable in operation. Despite having 4 SATA ports, only two ports operate at SATA 3 (6Gbps) speeds, the other two are SATA 2 (3Gbps) ports. Ethernet is handled by an onboard gigabit Realtek chip as standard 

During a stream in 2023 I was able to get this machine to run [[Windows Server 2000|'''''Windows Server 2000''''']] successfully. This proved quite stable and extremely performant over the newer Server 2003 R2 x64. This unit may be repurposed in future to run services atop that operating system version.</text>
    <sha1>122d28ff7244516c5fb2b4e11c0525f797515663</sha1>
  </revision>
  <revision>
    <id>30</id>
    <parentid>29</parentid>
    <timestamp>2024-09-02T10:53:34Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1629" xml:space="preserve">The Acer EasyStore H340 was a home NAS sold by Acer during the Windows Home Server era. Much like its "cousin" the [[HP MediaSmart EX495]] it came pre-loaded with [[Windows Home Server 2007]]


By default this device would come with 4x 1TB SATA 3.5" hard disks installed. The top most drive includes a warning label explaining that the operating system is installed on it and to be careful with removing or replacing the drive.

The machine originally shipped with an extremely anemic Intel Atom 230 CPU and 2GB of DDR2 memory as standard to compliment the storage. It also contains a single PCI-E slot for (small!) expansion cards.

Unfortunately my H340 suffered significant damage in shipping as the device was *extremely* poorly packaged. As a result the internals of the machine have been completely replaced.

At this time the machine has an ASUS AT4NM10T-I ITX motherboard installed. This board features an Atom D525 chip and can support up to 8GB of SODIMM (laptop) memory. This chip is roughly comparable to two Atom 230's "glued" together and is extremely unreliable in operation. Despite having 4 SATA ports, only two ports operate at SATA 3 (6Gbps) speeds, the other two are SATA 2 (3Gbps) ports. Ethernet is handled by an onboard gigabit Realtek chip as standard 

During a stream in 2023 I was able to get this machine to run [[Windows Server 2000|'''''Windows Server 2000''''']] successfully. This proved quite stable and extremely performant over the newer Server 2003 R2 x64. This unit may be repurposed in future to run services atop that operating system version.

[[File:Acer EasyStore Front.jpg|none|thumb]]</text>
    <sha1>9af3f8f1749361a91a986b3fe7053d7ad415294b</sha1>
  </revision>
  <revision>
    <id>31</id>
    <parentid>30</parentid>
    <timestamp>2024-09-02T10:54:12Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1703" xml:space="preserve">The Acer EasyStore H340 was a home NAS sold by Acer during the Windows Home Server era. Much like its "cousin" the [[HP MediaSmart EX495]] it came pre-loaded with [[Windows Home Server 2007]]


By default this device would come with 4x 1TB SATA 3.5" hard disks installed. The top most drive includes a warning label explaining that the operating system is installed on it and to be careful with removing or replacing the drive.

The machine originally shipped with an extremely anemic Intel Atom 230 CPU and 2GB of DDR2 memory as standard to compliment the storage. It also contains a single PCI-E slot for (small!) expansion cards.

Unfortunately my H340 suffered significant damage in shipping as the device was *extremely* poorly packaged. As a result the internals of the machine have been completely replaced.

At this time the machine has an ASUS AT4NM10T-I ITX motherboard installed. This board features an Atom D525 chip and can support up to 8GB of SODIMM (laptop) memory. This chip is roughly comparable to two Atom 230's "glued" together and is extremely unreliable in operation. Despite having 4 SATA ports, only two ports operate at SATA 3 (6Gbps) speeds, the other two are SATA 2 (3Gbps) ports. Ethernet is handled by an onboard gigabit Realtek chip as standard 

During a stream in 2023 I was able to get this machine to run [[Windows Server 2000|'''''Windows Server 2000''''']] successfully. This proved quite stable and extremely performant over the newer Server 2003 R2 x64. This unit may be repurposed in future to run services atop that operating system version.

[[File:Acer EasyStore Front.jpg|none|thumb|Front of unit]]
[[File:Rear view of EasyStore.jpg|none|thumb|Rear of unit]]</text>
    <sha1>f6de9c4a712787a63314c118005a087b62e6c24e</sha1>
  </revision>
  <revision>
    <id>32</id>
    <parentid>31</parentid>
    <timestamp>2024-09-02T11:02:12Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1701" xml:space="preserve">The Acer EasyStore H340 was a home NAS sold by Acer during the Windows Home Server era. Much like its "cousin" the [[HP MediaSmart EX495]] it came pre-loaded with [[Windows Home Server 2007]]

By default this device would come with 4x 1TB SATA 3.5" hard disks installed. The top most drive includes a warning label explaining that the operating system is installed on it and to be careful with removing or replacing the drive.

The machine originally shipped with an extremely anemic Intel Atom 230 CPU and 2GB of DDR2 memory as standard to compliment the storage. It also contains a single PCI-E slot for (small!) expansion cards.

Unfortunately my H340 suffered significant damage in shipping as the device was *extremely* poorly packaged. As a result the internals of the machine have been completely replaced.

At this time the machine has an ASUS AT4NM10T-I ITX motherboard installed. This board features an Atom D525 chip and can support up to 8GB of SODIMM (laptop) memory. This chip is roughly comparable to two Atom 230's "glued" together and is extremely unreliable in operation. Despite having 4 SATA ports, only two ports operate at SATA 3 (6Gbps) speeds, the other two are SATA 2 (3Gbps) ports. Ethernet is handled by an onboard gigabit Realtek chip as standard 

During a stream in 2023 I was able to get this machine to run [[Windows Server 2000|'''''Windows Server 2000''''']] successfully. This proved quite stable and extremely performant over the newer Server 2003 R2 x64. This unit may be repurposed in future to run services atop that operating system version.

[[File:Acer EasyStore Front.jpg|none|thumb|Front of unit]]
[[File:Rear view of EasyStore.jpg|none|thumb|Rear of unit]]</text>
    <sha1>9209c58d80aeaed08b7468886fbe70b0b45cd834</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:Acer EasyStore Front.jpg</title>
  <ns>6</ns>
  <id>9</id>
  <revision>
    <id>25</id>
    <timestamp>2024-09-02T10:31:32Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="27" xml:space="preserve">Acer EasyStore H340 (front)</text>
    <sha1>2c455ef655542477f3b337da02b47f7cf2e24458</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:Rear view of EasyStore.jpg</title>
  <ns>6</ns>
  <id>10</id>
  <revision>
    <id>26</id>
    <timestamp>2024-09-02T10:32:25Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="32" xml:space="preserve">Rear view of Acer EasyStore H340</text>
    <sha1>254f9ad2cb0b5a5826d09d98c67d6f8030796844</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:G4 MDD Front.jpg</title>
  <ns>6</ns>
  <id>11</id>
  <revision>
    <id>33</id>
    <timestamp>2024-09-02T11:56:24Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12" xml:space="preserve">G4 MDD front</text>
    <sha1>addb73a9f46a5cd0448b577d0687aa21eaf669c6</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:G4 MDD 1.42Ghz (rear).jpg</title>
  <ns>6</ns>
  <id>12</id>
  <revision>
    <id>34</id>
    <timestamp>2024-09-02T11:57:34Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="21" xml:space="preserve">G4 MDD 1.42Ghz (rear)</text>
    <sha1>f0739203ecc938d62f68d98f211dd7a8af8bf266</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:G4 MDD 1.25Ghz (rear).jpg</title>
  <ns>6</ns>
  <id>13</id>
  <revision>
    <id>35</id>
    <timestamp>2024-09-02T11:58:38Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="21" xml:space="preserve">G4 MDD 1.25Ghz (rear)</text>
    <sha1>f1e2462758c0a5a90dc83ab557e873d4c0259754</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Powermac G4</title>
  <ns>0</ns>
  <id>14</id>
  <revision>
    <id>36</id>
    <timestamp>2024-09-02T11:58:58Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Apple's PowerMac G4 "MDD" or "Mirrored Drive Door" units are common enough and have been documented heavily enough across the internet by people smarter than me that I don't have much to add about them here.    I currently own two units. A Dual 1.42Ghz "Firewire 800" (FW800) model and a Dual 1.25Ghz FW800 model.  === 1.42Ghz model details ===   This machine is outfitted with the maximum 2GB of memory (1.5GB under MacOS 9.2) and the fastest supported GPU, an Nvidia Ti4600..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2688" xml:space="preserve">Apple's PowerMac G4 "MDD" or "Mirrored Drive Door" units are common enough and have been documented heavily enough across the internet by people smarter than me that I don't have much to add about them here. 


I currently own two units. A Dual 1.42Ghz "Firewire 800" (FW800) model and a Dual 1.25Ghz FW800 model.

=== 1.42Ghz model details ===


This machine is outfitted with the maximum 2GB of memory (1.5GB under MacOS 9.2) and the fastest supported GPU, an Nvidia Ti4600


The 1.42Ghz model is also equipped with a SeriTek/1eVE2+2 expansion card. This card appears(?) to have been discontinued as the SeriTek "Yahoo" store is no longer operational. 


The SeriTek card provides a 64-bit PCI-X (266MB/s) interface for attaching two SATA II hard disks. The PCI-X bandwidth allows attached drives to operate near their theoretical maximum of 300MB/s (SATA II 3Gbps) however in operation due to the old, slow G4 CPU typical data transfer rates are roughly half that. This is still considerably faster than the ATA-66 IDE bus installed on the motherboard as standard.


The SeriTek card also contains an OpenFirmware compatible Boot ROM, allowing the card to be used to boot OS 9 natively. The additional I/O performance massively improves I/O bound workloads such as "StuffIt" and heavier apps such as ClassZilla.


The internals of the 1.42Ghz model have also been modified. The power supply has been replaced with a PicoPSU style unit for ATX PC's (with corresponding adapter cable) along with dual Noctua 40mm fans for additional cooling. The main CPU fan has been replaced with a 120mm Noctua "PPC" Industrial fan. This fan outputs considerably more airflow than the original fan, while maintaining comparable noise levels. The CPU has yet to be measured above 35C while in operation under this configuration.


At this time the machine currently operates with MacOS 9.2 and OS X 10.5.9 "Sorbet Leopard" from a 240GB SSD partitioned 50/50 between the two operating systems


The second port was originally configured with a second 120GB drive for PPC Linux. However the "nouveau" Linux driver causes system lockups due to (known) endianness issues on PowerPC platforms

==== 1.25Ghz model details ====


This machine is currently unused and lacks a graphics card. It was purchased for testing upgrading the [[Xserve G4]] with a faster dual processor CPU however this was unsuccessful. 


The unit has a SCSI card of currently known vendor as well as a dual gigabit PCI-X SFP NIC of unknown vendor

[[File:G4 MDD Front.jpg|none|thumb|G4 MDD front]]
[[File:G4 MDD 1.42Ghz (rear).jpg|none|thumb|G4 MDD 1.42Ghz (rear)]]
[[File:G4 MDD 1.25Ghz (rear).jpg|none|thumb|G4 MDD 1.25Ghz (rear)]]</text>
    <sha1>b7cab4434a989edf7469633567ac827030d43a9a</sha1>
  </revision>
  <revision>
    <id>37</id>
    <parentid>36</parentid>
    <timestamp>2024-09-02T11:59:27Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2682" xml:space="preserve">Apple's PowerMac G4 "MDD" or "Mirrored Drive Door" units are common enough and have been documented heavily enough across the internet by people smarter than me that I don't have much to add about them here. 


I currently own two units. A Dual 1.42Ghz "Firewire 800" (FW800) model and a Dual 1.25Ghz FW800 model.

== 1.42Ghz model details ==


This machine is outfitted with the maximum 2GB of memory (1.5GB under MacOS 9.2) and the fastest supported GPU, an Nvidia Ti4600


The 1.42Ghz model is also equipped with a SeriTek/1eVE2+2 expansion card. This card appears(?) to have been discontinued as the SeriTek "Yahoo" store is no longer operational. 


The SeriTek card provides a 64-bit PCI-X (266MB/s) interface for attaching two SATA II hard disks. The PCI-X bandwidth allows attached drives to operate near their theoretical maximum of 300MB/s (SATA II 3Gbps) however in operation due to the old, slow G4 CPU typical data transfer rates are roughly half that. This is still considerably faster than the ATA-66 IDE bus installed on the motherboard as standard.


The SeriTek card also contains an OpenFirmware compatible Boot ROM, allowing the card to be used to boot OS 9 natively. The additional I/O performance massively improves I/O bound workloads such as "StuffIt" and heavier apps such as ClassZilla.


The internals of the 1.42Ghz model have also been modified. The power supply has been replaced with a PicoPSU style unit for ATX PC's (with corresponding adapter cable) along with dual Noctua 40mm fans for additional cooling. The main CPU fan has been replaced with a 120mm Noctua "PPC" Industrial fan. This fan outputs considerably more airflow than the original fan, while maintaining comparable noise levels. The CPU has yet to be measured above 35C while in operation under this configuration.


At this time the machine currently operates with MacOS 9.2 and OS X 10.5.9 "Sorbet Leopard" from a 240GB SSD partitioned 50/50 between the two operating systems


The second port was originally configured with a second 120GB drive for PPC Linux. However the "nouveau" Linux driver causes system lockups due to (known) endianness issues on PowerPC platforms

== 1.25Ghz model details ==


This machine is currently unused and lacks a graphics card. It was purchased for testing upgrading the [[Xserve G4]] with a faster dual processor CPU however this was unsuccessful. 


The unit has a SCSI card of currently known vendor as well as a dual gigabit PCI-X SFP NIC of unknown vendor

[[File:G4 MDD Front.jpg|none|thumb|G4 MDD front]]
[[File:G4 MDD 1.42Ghz (rear).jpg|none|thumb|G4 MDD 1.42Ghz (rear)]]
[[File:G4 MDD 1.25Ghz (rear).jpg|none|thumb|G4 MDD 1.25Ghz (rear)]]</text>
    <sha1>352aa11b8740c570e33d1025a096e565af087b84</sha1>
  </revision>
  <revision>
    <id>38</id>
    <parentid>37</parentid>
    <timestamp>2024-09-02T11:59:51Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2695" xml:space="preserve">Apple's PowerMac G4 "MDD" or "Mirrored Drive Door" units are common enough and have been documented heavily enough across the internet by people smarter than me that I don't have much to add about them here. 


I currently own two units. A Dual 1.42Ghz "Firewire 800" (FW800) model and a Dual 1.25Ghz FW800 model.

== 1.42Ghz model details ==


This machine is outfitted with the maximum 2GB of memory (1.5GB under MacOS 9.2) and the fastest supported GPU, an Nvidia Ti4600


The 1.42Ghz model is also equipped with a SeriTek/1eVE2+2 expansion card. This card appears(?) to have been discontinued as the SeriTek "Yahoo" store is no longer operational. 


The SeriTek card provides a 64-bit PCI-X (266MB/s) interface for attaching two SATA II hard disks. The PCI-X bandwidth allows attached drives to operate near their theoretical maximum of 300MB/s (SATA II 3Gbps) however in operation due to the old, slow G4 CPU typical data transfer rates are roughly half that. This is still considerably faster than the ATA-66 IDE bus installed on the motherboard as standard.


The SeriTek card also contains an OpenFirmware compatible Boot ROM, allowing the card to be used to boot OS 9 natively. The additional I/O performance massively improves I/O bound workloads such as "StuffIt" and heavier apps such as ClassZilla.


The internals of the 1.42Ghz model have also been modified. The power supply has been replaced with a PicoPSU style unit for ATX PC's (with corresponding adapter cable) along with dual Noctua 40mm fans for additional cooling. The main CPU fan has been replaced with a 120mm Noctua "PPC" Industrial fan. This fan outputs considerably more airflow than the original fan, while maintaining comparable noise levels. The CPU has yet to be measured above 35C while in operation under this configuration.


At this time the machine currently operates with MacOS 9.2 and OS X 10.5.9 "Sorbet Leopard" from a 240GB SSD partitioned 50/50 between the two operating systems


The second port was originally configured with a second 120GB drive for PPC Linux. However the "nouveau" Linux driver causes system lockups due to (known) endianness issues on PowerPC platforms

== 1.25Ghz model details ==


This machine is currently unused and lacks a graphics card. It was purchased for testing upgrading the [[Xserve G4]] with a faster dual processor CPU however this was unsuccessful. 


The unit has a SCSI card of currently known vendor as well as a dual gigabit PCI-X SFP NIC of unknown vendor

== Images ==
[[File:G4 MDD Front.jpg|none|thumb|G4 MDD front]]
[[File:G4 MDD 1.42Ghz (rear).jpg|none|thumb|G4 MDD 1.42Ghz (rear)]]
[[File:G4 MDD 1.25Ghz (rear).jpg|none|thumb|G4 MDD 1.25Ghz (rear)]]</text>
    <sha1>4f3a1a8aa25fd5b14119450cb16c9b8dfc7441aa</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:Mac G5 Quad (front).jpg</title>
  <ns>6</ns>
  <id>15</id>
  <revision>
    <id>39</id>
    <timestamp>2024-09-07T07:49:24Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19" xml:space="preserve">Mac G5 Quad (front)</text>
    <sha1>649a9a702544b3f985ba633120a6c77d52b37f46</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:Mac G5 Quad (rear).jpg</title>
  <ns>6</ns>
  <id>16</id>
  <revision>
    <id>40</id>
    <timestamp>2024-09-07T07:50:08Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18" xml:space="preserve">Mac G5 Quad (rear)</text>
    <sha1>bb08d9f3fbedbd6295ac5313dba64ba38cd1942d</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Powermac G5</title>
  <ns>0</ns>
  <id>17</id>
  <revision>
    <id>41</id>
    <timestamp>2024-09-07T07:50:36Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Apple's G5 Powermac's are rather infamous, being Apple's "last gasp" of PowerPC. The PowerMac G5 '''''Quad''''' in particular is easily among Apple's most unloved and slapdash engineered products.    Due to me taking the suggestion of a friend far too literally (ilu Ben please don't hate me) I own '''''seven''''' G5 Quads   '''Despite this only one of them is functional!'''   All Mac G5 Quads were made with "water cooling" loops, due to the thermal output of the CPU's at..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2712" xml:space="preserve">Apple's G5 Powermac's are rather infamous, being Apple's "last gasp" of PowerPC. The PowerMac G5 '''''Quad''''' in particular is easily among Apple's most unloved and slapdash engineered products. 


Due to me taking the suggestion of a friend far too literally (ilu Ben please don't hate me) I own '''''seven''''' G5 Quads


'''Despite this only one of them is functional!'''


All Mac G5 Quads were made with "water cooling" loops, due to the thermal output of the CPU's at the time. (105 watts of heat in 2005 is a lot, though with what Intel puts out these days seems rather pedestrian!) '''''however calling it water cooling is incorrect.''''' It's actually radiator fluid! Specifically "Dex-Cool" or AntiFreeze. 


The water cooling loops were designed and manufactured by American car maker GM Auto's engine radiator subsidiary. Your G5 Mac literally uses car parts to cool its CPU's! It's any wonder Apple ditched IBM. 


It's possible (and desirable) to replace the entire cooling assembly, the 68KMLA forms calls it the "New Blood Mod" though I have not yet performed the repairs on my units due to cost.


Anyway. The one singular G5 Quad I have working is effectively a maxed out G5 Quad. The specifications are listed below

4x 2.5Ghz PPC64 G5 CPU's (2c/2t)

16GB DDR2-667 (or 800? I forget the max speed) RAM. In theory the chipset can support 32GB but nobody has managed to get one operating with that much memory.

Two 240GB SATA SSD's. '''Due to Apple's flaky SATA controller most drives won't work as negotiating SATA 3 speeds down to SATA 1 causes the controller to instead hang. You may want to find drives that have a SATA1 jumper option to prevent this!'''


As the G5 Quad contains four PCI-E slots (of varying bandwidths) I've arranged them as follows


240GB NVME drive via PCI-E adapter (PCI-E x4)

10G Intel X520 SFP ethernet adapter (PCI-E x8)

Slot blocked by dual-slot GPU (PCI-E x8 otherwise)

ATI Radeon X1950 (vBIOS flashed for Mac operation)


The NVME drive is purely used for Linux. GRUB will load a kernel from the SATA drive and is configured to pass root=/dev/nvme0n1p1 allowing the root filesystem to be run off NVME. As a bonus, moving the Mac "k2_sata" kernel module to be loaded on-demand instead of at boot will save 5 seconds off the Linux kernel boot time.


The system currently dual boots OS X 10.5.9 "Sorbet" Leopard and Gentoo PPC64


Unfortunately G5 Quads cannot run Tiger due to missing fan control drivers. If installed, the fans will eventually ramp to 100% as a failsafe mechanism. 

[[File:Mac G5 Quad (front).jpg|alt=Mac G5 Quad (front)|none|thumb|Mac G5 Quad (front)]]
[[File:Mac G5 Quad (rear).jpg|alt=Mac G5 Quad (rear)|none|thumb|Mac G5 Quad (rear)]]</text>
    <sha1>f568431ec7d33c042c4f6273a952b50c41b96cff</sha1>
  </revision>
  <revision>
    <id>42</id>
    <parentid>41</parentid>
    <timestamp>2024-09-07T08:05:58Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2537" xml:space="preserve">Apple's G5 Powermac's are rather infamous, being Apple's "last gasp" of PowerPC. The PowerMac G5 '''''Quad''''' in particular is easily among Apple's most unloved and slapdash engineered products. 


Due to me taking the suggestion of a friend far too literally (ilu Ben please don't hate me) I own '''''seven''''' G5 Quads


'''Despite this only one of them is functional!'''


All Mac G5 Quads were made with "water cooling" loops, due to the thermal output of the CPU's at the time. (105 watts of heat in 2005 is a lot, though with what Intel puts out these days seems rather pedestrian!) '''''however calling it water cooling is incorrect.''''' It's actually radiator fluid! Specifically "Dex-Cool" or AntiFreeze. 


The water cooling loops were designed and manufactured by American car maker GM Auto's engine radiator subsidiary. Your G5 Mac literally uses car parts to cool its CPU's! It's any wonder Apple ditched IBM. 


It's possible (and desirable) to replace the entire cooling assembly, the 68KMLA forms calls it the "New Blood Mod" though I have not yet performed the repairs on my units due to cost.


Anyway. The one singular G5 Quad I have working is effectively a maxed out G5 Quad. The specifications are listed below

4x 2.5Ghz PPC64 G5 CPU's (2c/2t)

16GB DDR2-667 (or 800? I forget the max speed) RAM. In theory the chipset can support 32GB but nobody has managed to get one operating with that much memory.

Two 240GB SATA SSD's. '''Due to Apple's flaky SATA controller most drives won't work as negotiating SATA 3 speeds down to SATA 1 causes the controller to instead hang. You may want to find drives that have a SATA1 jumper option to prevent this!'''


As the G5 Quad contains four PCI-E slots (of varying bandwidths) I've arranged them as follows


240GB NVME drive via PCI-E adapter (PCI-E x4)

10G Intel X520 SFP ethernet adapter (PCI-E x8)

Slot blocked by dual-slot GPU (PCI-E x8 otherwise)

ATI Radeon X1950 (vBIOS flashed for Mac operation)


The NVME drive is purely used for Linux. GRUB will load a kernel from the SATA drive and is configured to pass root=/dev/nvme0n1p1 allowing the root filesystem to be run off NVME. As a bonus, moving the Mac "k2_sata" kernel module to be loaded on-demand instead of at boot will save 5 seconds off the Linux kernel boot time.


The system currently dual boots OS X 10.5.9 "Sorbet" Leopard and Gentoo PPC64


Unfortunately G5 Quads cannot run Tiger due to missing fan control drivers. If installed, the fans will eventually ramp to 100% as a failsafe mechanism.</text>
    <sha1>90f31819c66b06a705421475ce5eafa441e3ad17</sha1>
  </revision>
  <revision>
    <id>43</id>
    <parentid>42</parentid>
    <timestamp>2024-09-07T08:06:26Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2593" xml:space="preserve">Apple's G5 Powermac's are rather infamous, being Apple's "last gasp" of PowerPC. The PowerMac G5 '''''Quad''''' in particular is easily among Apple's most unloved and slapdash engineered products. 


Due to me taking the suggestion of a friend far too literally (ilu Ben please don't hate me) I own '''''seven''''' G5 Quads


'''Despite this only one of them is functional!'''


All Mac G5 Quads were made with "water cooling" loops, due to the thermal output of the CPU's at the time. (105 watts of heat in 2005 is a lot, though with what Intel puts out these days seems rather pedestrian!) '''''however calling it water cooling is incorrect.''''' It's actually radiator fluid! Specifically "Dex-Cool" or AntiFreeze. 


The water cooling loops were designed and manufactured by American car maker GM Auto's engine radiator subsidiary. Your G5 Mac literally uses car parts to cool its CPU's! It's any wonder Apple ditched IBM. 


It's possible (and desirable) to replace the entire cooling assembly, the 68KMLA forms calls it the "New Blood Mod" though I have not yet performed the repairs on my units due to cost.


Anyway. The one singular G5 Quad I have working is effectively a maxed out G5 Quad. The specifications are listed below

4x 2.5Ghz PPC64 G5 CPU's (2c/2t)

16GB DDR2-667 (or 800? I forget the max speed) RAM. In theory the chipset can support 32GB but nobody has managed to get one operating with that much memory.

Two 240GB SATA SSD's. '''Due to Apple's flaky SATA controller most drives won't work as negotiating SATA 3 speeds down to SATA 1 causes the controller to instead hang. You may want to find drives that have a SATA1 jumper option to prevent this!'''


As the G5 Quad contains four PCI-E slots (of varying bandwidths) I've arranged them as follows


240GB NVME drive via PCI-E adapter (PCI-E x4)

10G Intel X520 SFP ethernet adapter (PCI-E x8)

Slot blocked by dual-slot GPU (PCI-E x8 otherwise)

ATI Radeon X1950 (vBIOS flashed for Mac operation)


The NVME drive is purely used for Linux. GRUB will load a kernel from the SATA drive and is configured to pass root=/dev/nvme0n1p1 allowing the root filesystem to be run off NVME. As a bonus, moving the Mac "k2_sata" kernel module to be loaded on-demand instead of at boot will save 5 seconds off the Linux kernel boot time.


The system currently dual boots OS X 10.5.9 "Sorbet" Leopard and Gentoo PPC64


Unfortunately G5 Quads cannot run Tiger due to missing fan control drivers. If installed, the fans will eventually ramp to 100% as a failsafe mechanism.

[[File:Mac G5 Quad (front).jpg|thumb|G5 Quad (Front)]]</text>
    <sha1>549c4fdecd6b86737857d9e69c00bb7190cf3afb</sha1>
  </revision>
  <revision>
    <id>44</id>
    <parentid>43</parentid>
    <timestamp>2024-09-07T08:07:08Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2678" xml:space="preserve"> 
Apple's G5 Powermac's are rather infamous, being Apple's "last gasp" of PowerPC. The PowerMac G5 '''''Quad''''' in particular is easily among Apple's most unloved and slapdash engineered products. 


Due to me taking the suggestion of a friend far too literally (ilu Ben please don't hate me) I own '''''seven''''' G5 Quads


'''Despite this only one of them is functional!'''


All Mac G5 Quads were made with "water cooling" loops, due to the thermal output of the CPU's at the time. (105 watts of heat in 2005 is a lot, though with what Intel puts out these days seems rather pedestrian!) '''''however calling it water cooling is incorrect.''''' It's actually radiator fluid! Specifically "Dex-Cool" or AntiFreeze. 


The water cooling loops were designed and manufactured by American car maker GM Auto's engine radiator subsidiary. Your G5 Mac literally uses car parts to cool its CPU's! It's any wonder Apple ditched IBM. 


It's possible (and desirable) to replace the entire cooling assembly, the 68KMLA forms calls it the "New Blood Mod" though I have not yet performed the repairs on my units due to cost.


Anyway. The one singular G5 Quad I have working is effectively a maxed out G5 Quad. The specifications are listed below

4x 2.5Ghz PPC64 G5 CPU's (2c/2t)

16GB DDR2-667 (or 800? I forget the max speed) RAM. In theory the chipset can support 32GB but nobody has managed to get one operating with that much memory.

Two 240GB SATA SSD's. '''Due to Apple's flaky SATA controller most drives won't work as negotiating SATA 3 speeds down to SATA 1 causes the controller to instead hang. You may want to find drives that have a SATA1 jumper option to prevent this!'''


As the G5 Quad contains four PCI-E slots (of varying bandwidths) I've arranged them as follows


240GB NVME drive via PCI-E adapter (PCI-E x4)

10G Intel X520 SFP ethernet adapter (PCI-E x8)

Slot blocked by dual-slot GPU (PCI-E x8 otherwise)

ATI Radeon X1950 (vBIOS flashed for Mac operation)


The NVME drive is purely used for Linux. GRUB will load a kernel from the SATA drive and is configured to pass root=/dev/nvme0n1p1 allowing the root filesystem to be run off NVME. As a bonus, moving the Mac "k2_sata" kernel module to be loaded on-demand instead of at boot will save 5 seconds off the Linux kernel boot time.


The system currently dual boots OS X 10.5.9 "Sorbet" Leopard and Gentoo PPC64


Unfortunately G5 Quads cannot run Tiger due to missing fan control drivers. If installed, the fans will eventually ramp to 100% as a failsafe mechanism.

[[File:Mac G5 Quad (front).jpg|thumb|G5 Quad (Front)|none]]
[[File:Mac G5 Quad (rear).jpg|alt=G5 Quad (Rear)|none|thumb|G5 Quad (Rear)]]</text>
    <sha1>8f54353e6556917df1481f66aaee09619187c270</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:Xserve G4 (Front).jpg</title>
  <ns>6</ns>
  <id>19</id>
  <revision>
    <id>46</id>
    <timestamp>2024-09-07T08:19:34Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17" xml:space="preserve">Xserve G4 (Front)</text>
    <sha1>0b445a4c62dc025b48d842937288a600124478ad</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Xserve G4</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>47</id>
    <timestamp>2024-09-07T08:20:14Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "So, eBay has a "Make Offer" function that buyers and sellers can use for items on the site.   When you submit an offer, the seller has 24 hours to respond.   Turns out, if the auction has less than 24 hours remaining '''''and zero bids''''' eBay will auto-accept the "Best Offer" instead.    So that's how I got a G4 Xserve for $50 (the seller wanted like $300)   The Xserve G4 I have is the [https://everymac.com/systems/apple/xserve/specs/xserve_g4_1ghz.html absolute base..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1265" xml:space="preserve">So, eBay has a "Make Offer" function that buyers and sellers can use for items on the site.


When you submit an offer, the seller has 24 hours to respond.


Turns out, if the auction has less than 24 hours remaining '''''and zero bids''''' eBay will auto-accept the "Best Offer" instead. 


So that's how I got a G4 Xserve for $50 (the seller wanted like $300)


The Xserve G4 I have is the [https://everymac.com/systems/apple/xserve/specs/xserve_g4_1ghz.html absolute base specification 1.0Ghz single processor unit] however the RAM has been upgraded to the maximum 2GB allowed. I had previously attempted upgrading it with a 1.25Ghz dual processor card from a G4 MDD "donor" system but the machine failed to POST (Chime?) and was downgraded back to stock.


The only other modification was installing all four IDE disk bays and configuring them with StarTech SATA adapters for future use. 


'''Due to the significantly more performant G5 Xserve (and the G5 Quad PowerMac) there currently are not any plans to bring this machine into service'''


also I forgot to take a shot of the rear of the unit. However with no expansion cards installed there's nothing of interest on it compared to a stock unit

[[File:Xserve G4 (Front).jpg|none|thumb|Xserve G4 (Front)]]</text>
    <sha1>9de379fda4de7a7d981ef1053d8ae1a4ac2ef1fd</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:Xserve G5 (Front).jpg</title>
  <ns>6</ns>
  <id>21</id>
  <revision>
    <id>48</id>
    <timestamp>2024-09-07T08:35:42Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17" xml:space="preserve">Xserve G5 (Front)</text>
    <sha1>0fcab9a7f7209e3e27ab0c8fef4743d846e513f6</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:Xserve G5 (Rear).jpg</title>
  <ns>6</ns>
  <id>22</id>
  <revision>
    <id>49</id>
    <timestamp>2024-09-07T08:36:57Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16" xml:space="preserve">Xserve G5 (Rear)</text>
    <sha1>bfa46a80cd024a448d0fcdf3c3fc2cd8a862a674</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Xserve G5</title>
  <ns>0</ns>
  <id>23</id>
  <revision>
    <id>50</id>
    <timestamp>2024-09-07T08:37:54Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Unlike it's little brother the [[Xserve G4]] the Xserve G5 is a significant step up in capability and usefulness.   The unit I own is the fastest Xserve G5 model sold. The 2.3Ghz "Dual Processor" G5.    Unlike its "cheese grater sibling" the [[Powermac G5|G5 Quad]] the DP Xserve is based on the older G5 lineage, featuring '''''PCI-X''''' rather than PCI-E slots. This significantly reduces its expandability as 64-bit PCI-X slots are limited to approximately 266MB/s of ban..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1355" xml:space="preserve">Unlike it's little brother the [[Xserve G4]] the Xserve G5 is a significant step up in capability and usefulness.


The unit I own is the fastest Xserve G5 model sold. The 2.3Ghz "Dual Processor" G5. 


Unlike its "cheese grater sibling" the [[Powermac G5|G5 Quad]] the DP Xserve is based on the older G5 lineage, featuring '''''PCI-X''''' rather than PCI-E slots. This significantly reduces its expandability as 64-bit PCI-X slots are limited to approximately 266MB/s of bandwidth, versus the 4GB/s of a PCI-E 1.0 16x slot in the G5 Quad.


This limitation means we're stuck with only gigabit ethernet rather than the 10G of the Quad. We also only get two PCI-X slots in total instead of three. Of which at least one requires a video card to be installed to operate the unit (unless remote administration tools are installed)


Another limitation (correction?) despite what EveryMac claims, the unit is not capable of 16GB of memory. Only 8GB can be installed (I learned this the hard way!)


'''At present the G5 is paired with a 120GB SATA disk with OS X 10.5.9 "Sorbet" Leopard. However at time of writing the machine is currently unused, pending decisions about what tasks to run on it'''

[[File:Xserve G5 (Front).jpg|alt=Xserve G5 (Front)|none|thumb|Xserve G5 (Front)]]
[[File:Xserve G5 (Rear).jpg|alt=Xserve G5 (Rear)|none|thumb|Xserve G5 (Rear)]]</text>
    <sha1>b69e6f278225f93a33c683c081c1ee22e668c4dd</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:Cobalt RaQ4 (Front).jpg</title>
  <ns>6</ns>
  <id>24</id>
  <revision>
    <id>51</id>
    <timestamp>2024-09-07T08:59:32Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19" xml:space="preserve">Cobalt RaQ4 (Front)</text>
    <sha1>e5a69bd618870fe740364f6afd93d1b2ab1053c6</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:Cobalt RaQ4 (Rear).jpg</title>
  <ns>6</ns>
  <id>25</id>
  <revision>
    <id>52</id>
    <timestamp>2024-09-07T09:00:25Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18" xml:space="preserve">Cobalt RaQ4 (Rear)</text>
    <sha1>ffbba25e7bb860132bc8720d1149611b0415d681</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>Cobalt RaQ</title>
  <ns>0</ns>
  <id>26</id>
  <revision>
    <id>53</id>
    <timestamp>2024-09-07T09:00:58Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "There's not a lot of super useful information to add about specifically the Cobalt RaQ units that isn't already covered by the [[Cobalt Qube 3|Qube 3]]. The RaQ 3/4 are effectively Qube 3's in a 1U server formfactor.    Arguably due to the removal of the PCI slot and single IDE port they're '''''worse''''' than the Qube 3 in terms of overall functionality. The power supply is also custom and may also be prone to capacitor leakage similar to the Qube 3 itself.   If you wo..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="905" xml:space="preserve">There's not a lot of super useful information to add about specifically the Cobalt RaQ units that isn't already covered by the [[Cobalt Qube 3|Qube 3]]. The RaQ 3/4 are effectively Qube 3's in a 1U server formfactor. 


Arguably due to the removal of the PCI slot and single IDE port they're '''''worse''''' than the Qube 3 in terms of overall functionality. The power supply is also custom and may also be prone to capacitor leakage similar to the Qube 3 itself.


If you would like to a PCI slot can be soldered back on to the Qube 3, along with the hardware for the second IDE port and other rear I/O ports.


'''Currently the RaQ4 is unused and is unlikely to be used in the future due to its limited hardware functionality''' 

[[File:Cobalt RaQ4 (Front).jpg|alt=Cobalt RaQ4 (Front)|none|thumb|Cobalt RaQ4 (Front)]]
[[File:Cobalt RaQ4 (Rear).jpg|alt=Cobalt RaQ4 (Rear)|none|thumb|Cobalt RaQ4 (Rear)]]</text>
    <sha1>86648657c8ec5a12ace6c5927736ebc5cf8427d5</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:PowerEdge 2500 (motherboard).jpg</title>
  <ns>6</ns>
  <id>27</id>
  <revision>
    <id>54</id>
    <timestamp>2024-09-07T09:07:39Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="28" xml:space="preserve">PowerEdge 2500 (motherboard)</text>
    <sha1>808e60f800dadb742f8ae90dfaf8a3d2c4e3da0b</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:PowerEdge 2500 (RAM stick).jpg</title>
  <ns>6</ns>
  <id>28</id>
  <revision>
    <id>55</id>
    <timestamp>2024-09-07T09:08:24Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="26" xml:space="preserve">PowerEdge 2500 (RAM stick)</text>
    <sha1>6ff8b346a69f6f61af0522f554c7476f6d25178e</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:PowerEdge 2500 (rear).jpg</title>
  <ns>6</ns>
  <id>29</id>
  <revision>
    <id>56</id>
    <timestamp>2024-09-07T09:08:59Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="21" xml:space="preserve">PowerEdge 2500 (rear)</text>
    <sha1>6044bfdd2c5ae872c48cbf15736fedecc03f6991</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>PowerEdge 2500</title>
  <ns>0</ns>
  <id>30</id>
  <revision>
    <id>57</id>
    <timestamp>2024-09-07T09:09:13Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "A $50 Re-PC sale in 2022. Unfortunately this unit was sold claiming to contain dual Pentium 3's, it is only outfitted with a single CPU.    At this time I have little documentation on this unit presently as I opened it to simply verify the state of its capacitors before realizing that it was only equipped with a single CPU    Once I get an extra VRM for the unit and upgrade the processors I will likely look into what functionality the server can be used for  File:Power..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="780" xml:space="preserve">A $50 Re-PC sale in 2022. Unfortunately this unit was sold claiming to contain dual Pentium 3's, it is only outfitted with a single CPU. 


At this time I have little documentation on this unit presently as I opened it to simply verify the state of its capacitors before realizing that it was only equipped with a single CPU 


Once I get an extra VRM for the unit and upgrade the processors I will likely look into what functionality the server can be used for

[[File:PowerEdge 2500 (motherboard).jpg|alt=PowerEdge 2500 (motherboard)|none|thumb|PowerEdge 2500 (motherboard)]]
[[File:PowerEdge 2500 (RAM stick).jpg|alt=PowerEdge 2500 (RAM stick)|none|thumb|PowerEdge 2500 (RAM stick)]]
[[File:PowerEdge 2500 (rear).jpg|alt=PowerEdge 2500 (rear)|none|thumb|PowerEdge 2500 (rear)]]</text>
    <sha1>36d82580c0864cc73fe770610b11265492a6bd0e</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>DEC AlphaServer 2100</title>
  <ns>0</ns>
  <id>31</id>
  <revision>
    <id>58</id>
    <timestamp>2024-09-10T06:36:51Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Thanks to a member of the Seattle Retro Computing Society I have a DEC Alpha 2100/275    I don't really know much *about* this machine yet. I'm told it did work by the guy who sold it to me. Conveniently he also furnished me with almost enough spare parts to build a whole second machine   '''At this time the machine is currently *unused* because it weighs 200 pounds and needs to be re-assembled and brought into service'''"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="425" xml:space="preserve">Thanks to a member of the Seattle Retro Computing Society I have a DEC Alpha 2100/275 


I don't really know much *about* this machine yet. I'm told it did work by the guy who sold it to me. Conveniently he also furnished me with almost enough spare parts to build a whole second machine


'''At this time the machine is currently *unused* because it weighs 200 pounds and needs to be re-assembled and brought into service'''</text>
    <sha1>cf818a6e9271b6ebfeadc8b710be6159e399a842</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:HP EX495 (Front).jpg</title>
  <ns>6</ns>
  <id>32</id>
  <revision>
    <id>59</id>
    <timestamp>2024-09-10T06:48:14Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16" xml:space="preserve">HP EX495 (Front)</text>
    <sha1>e6b8d7fc1b670442ed1a77770befa90d791f3290</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:HP EX495 (Rear).jpg</title>
  <ns>6</ns>
  <id>33</id>
  <revision>
    <id>60</id>
    <timestamp>2024-09-10T06:48:42Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15" xml:space="preserve">HP EX495 (Rear)</text>
    <sha1>eaccfde2eb08eb9f018cdaffa65d0209c36eed2b</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>HP MediaSmart EX495</title>
  <ns>0</ns>
  <id>34</id>
  <revision>
    <id>61</id>
    <timestamp>2024-09-10T06:48:51Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Microsoft's first (and so far, only) attempt to break into the then much smaller "home NAS" market. (Ironically Synology was founded in the year 2000 by an ex-Microsoft employee)   The EX495 and its brother?...cousin? whatever. The [[Acer EasyStore H340|Acer EasyStore]] (along with several other devices that I don't own) were a fleet of home NAS appliances sold by large OEM's for consumers.    The main selling point (I guess?) was the inclusion of "Windows Home Server"...."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1711" xml:space="preserve">Microsoft's first (and so far, only) attempt to break into the then much smaller "home NAS" market. (Ironically Synology was founded in the year 2000 by an ex-Microsoft employee)


The EX495 and its brother?...cousin? whatever. The [[Acer EasyStore H340|Acer EasyStore]] (along with several other devices that I don't own) were a fleet of home NAS appliances sold by large OEM's for consumers. 


The main selling point (I guess?) was the inclusion of "Windows Home Server". A re-skin of Windows Small Business Server 2003 with a web UI and some PC administration software attached. Unsurprisingly both of these features are long-defunct now


The HP is significantly more capable than its Acer counterpart. Its stock configuration can be modified with a larger PSU, additional RAM can be installed and the '''''miserable''''' stock [https://ark.intel.com/content/www/us/en/ark/products/29734/intel-celeron-processor-420-512k-cache-1-60-ghz-800-mhz-fsb.html Celeron 420 CPU] can be replaced with a much more capable Core 2 Quad '''Q9550s''' (the S is important as it needs to be low power!) or an equivalent Xeon if you prefer. 


To that end the unit I own (pictured below) is currently outfitted with all of the described upgrades. I have also replaced the rear case fans with 92mm Noctua fans for extra quietness


'''At this time the unit is not currently in active use as I do not have 3.5" hard disks to install into it. Due to the age of the system it also does not support 2TB+ (GPT formatted) disks without swapping the OS for Linux or similar'''

[[File:HP EX495 (Front).jpg|alt=HP EX495 (Front)|none|thumb|HP EX495 (Front)]]
[[File:HP EX495 (Rear).jpg|alt=HP EX495 (Rear)|none|thumb|HP EX495 (Rear)]]</text>
    <sha1>6cd2f93ca7f50c1185fec04fd2f39a373466454b</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:HP KAYAK (Front).jpg</title>
  <ns>6</ns>
  <id>35</id>
  <revision>
    <id>62</id>
    <timestamp>2024-09-10T06:52:18Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16" xml:space="preserve">HP KAYAK (Front)</text>
    <sha1>631097990f9b473cd945aaae1d02975ff570c89c</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:HP KAYAK (Rear).jpg</title>
  <ns>6</ns>
  <id>36</id>
  <revision>
    <id>63</id>
    <timestamp>2024-09-10T06:53:18Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15" xml:space="preserve">HP KAYAK (Rear)</text>
    <sha1>96eba51d7c2f212ab95ebe2fdad47a3549c6bb8b</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>SGI Octane</title>
  <ns>0</ns>
  <id>38</id>
  <revision>
    <id>65</id>
    <timestamp>2024-09-10T06:54:15Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Technically not *my* machine, this computer is on "indefinite" loan from a member of the local hackerspace pending repair and restoration to working order   At this time I do not have any additional information to add about it"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="226" xml:space="preserve">Technically not *my* machine, this computer is on "indefinite" loan from a member of the local hackerspace pending repair and restoration to working order


At this time I do not have any additional information to add about it</text>
    <sha1>28b5429e5285c50866d79e424531e4a560dd9f83</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:SGI 320 (front).jpg</title>
  <ns>6</ns>
  <id>39</id>
  <revision>
    <id>66</id>
    <timestamp>2024-09-10T07:10:43Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15" xml:space="preserve">SGI 320 (front)</text>
    <sha1>8fdf34509d6727e3086ede54b7573432136b0607</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:SGI 320 (rear).jpg</title>
  <ns>6</ns>
  <id>40</id>
  <revision>
    <id>67</id>
    <timestamp>2024-09-10T07:11:01Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14" xml:space="preserve">SGI 320 (rear)</text>
    <sha1>7862b0a87a2f2cd79c7056119777bff5ae00a217</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>SGI Visual Workstation 320</title>
  <ns>0</ns>
  <id>41</id>
  <revision>
    <id>68</id>
    <timestamp>2024-09-10T07:11:10Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "SGI's...frankly bizarre attempt to break into the x86 workstation world. The Visual Workstation series are seemingly more fondly remembered for their weird quirks and sheer limitations than any usefulness they brought to the market.   The SGI Visual Workstation (both 320 and 540) models are '''''NOT''''' PC's. They run x86 processors but everything surrounding them is completely custom  * Instead of a BIOS they use the "ARC" Firmware loader  * Most of the system is chain..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1511" xml:space="preserve">SGI's...frankly bizarre attempt to break into the x86 workstation world. The Visual Workstation series are seemingly more fondly remembered for their weird quirks and sheer limitations than any usefulness they brought to the market.


The SGI Visual Workstation (both 320 and 540) models are '''''NOT''''' PC's. They run x86 processors but everything surrounding them is completely custom

* Instead of a BIOS they use the "ARC" Firmware loader

* Most of the system is chained behind the "Cobalt", "Lithium" and "Arsenic" chips. These are custom ASIC chips that control most of the system functionality including graphics, sound, access to the "UMA" high-bandwidth memory, the video ports and the (non-functional on 320 series) firewire ports. All x86 peripherals (IDE, RTC and others) are "slaved" behind this chip

* The PCI slots are non-standard voltage at 3.3 volts rather than 5 volts. Making it virtually impossible to add expansion cards to the device


Additionally due to the custom firmware (ARC) and weird ASIC chips, the only two supported OS's are Windows NT4 and Windows 2000. XP won't even boot on this machine. 


Linux support was removed many years ago, though due to lack of interest from SGI was never really supported anyway (no accelerated X server among other missing hardware functionality)


'''At this time this unit is not in use'''

[[File:SGI 320 (front).jpg|alt=SGI 320 (front)|none|thumb|SGI 320 (front)]]
[[File:SGI 320 (rear).jpg|alt=SGI 320 (rear)|none|thumb|SGI 320 (rear)]]</text>
    <sha1>d96b7b6b52089b1fa7ff2ea9d546deb287278113</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:Netra T1 (front).jpg</title>
  <ns>6</ns>
  <id>42</id>
  <revision>
    <id>69</id>
    <timestamp>2024-09-10T07:14:45Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16" xml:space="preserve">Netra T1 (front)</text>
    <sha1>eeac1921f9b009e1e816930f9ee1ededeb652229</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:Netra T1 (Rear).jpg</title>
  <ns>6</ns>
  <id>43</id>
  <revision>
    <id>70</id>
    <timestamp>2024-09-10T07:17:28Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15" xml:space="preserve">Netra T1 (Rear)</text>
    <sha1>ff8cfb502f8a43b5bca9e0ee5dc154bc4d7a5fd2</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>Netra T1</title>
  <ns>0</ns>
  <id>44</id>
  <revision>
    <id>71</id>
    <timestamp>2024-09-10T07:17:44Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Along with its much larger brother the [[Sunfire 420R]] the Netra T1 100 is one of the several pieces of Sun equipment in my collection  At this time I don't have much information to post about it. I have not powered any of the Sun equipment on to investigate it deeper  Also the face plate fell off. Though apparently that's common with the brittle plastic [[File:Netra T1 (front).jpg|none|thumb|Netra T1 (front)]] File:Netra T1 (Rear).jpg|alt=Netra T1 (Rear)|none|thumb|N..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="491" xml:space="preserve">Along with its much larger brother the [[Sunfire 420R]] the Netra T1 100 is one of the several pieces of Sun equipment in my collection

At this time I don't have much information to post about it. I have not powered any of the Sun equipment on to investigate it deeper

Also the face plate fell off. Though apparently that's common with the brittle plastic
[[File:Netra T1 (front).jpg|none|thumb|Netra T1 (front)]]
[[File:Netra T1 (Rear).jpg|alt=Netra T1 (Rear)|none|thumb|Netra T1 (Rear)]]</text>
    <sha1>6a2a552ec44efba013cbc4327803185ab6662a3f</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:Sunfire 420R (Front).jpg</title>
  <ns>6</ns>
  <id>46</id>
  <revision>
    <id>73</id>
    <timestamp>2024-09-10T07:21:21Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20" xml:space="preserve">Sunfire 420R (Front)</text>
    <sha1>c38c0cedd7b331f8670d1ddc3b6562c70e6bbe89</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:Sunfire 420R (Back).jpg</title>
  <ns>6</ns>
  <id>47</id>
  <revision>
    <id>74</id>
    <timestamp>2024-09-10T07:21:50Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19" xml:space="preserve">Sunfire 420R (Back)</text>
    <sha1>69a8b852bda0d79f8d96d4b12fba856c2fffe2bd</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>SunFire Enterprise 420R</title>
  <ns>0</ns>
  <id>48</id>
  <revision>
    <id>75</id>
    <timestamp>2024-09-10T07:22:03Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The biggest Sun in my collection by far. The Sunfire Enterprise 420R is an 80+ pound beast of metal and loud    It will likely be the first machine of the Suns I bring back to life, so watch this page for updates! [[File:Sunfire 420R (Front).jpg|alt=Sunfire 420R (Front)|none|thumb|Sunfire 420R (Front)]] [[File:Sunfire 420R (Back).jpg|alt=Sunfire 420R (Rear)|none|thumb|Sunfire 420R (Rear)]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="392" xml:space="preserve">The biggest Sun in my collection by far. The Sunfire Enterprise 420R is an 80+ pound beast of metal and loud 


It will likely be the first machine of the Suns I bring back to life, so watch this page for updates!
[[File:Sunfire 420R (Front).jpg|alt=Sunfire 420R (Front)|none|thumb|Sunfire 420R (Front)]]
[[File:Sunfire 420R (Back).jpg|alt=Sunfire 420R (Rear)|none|thumb|Sunfire 420R (Rear)]]</text>
    <sha1>a9fee50e80b3ab01779c644dafacec393941955b</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:Sun Ultra 10 (front).jpg</title>
  <ns>6</ns>
  <id>49</id>
  <revision>
    <id>76</id>
    <timestamp>2024-09-10T07:22:46Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20" xml:space="preserve">Sun Ultra 10 (front)</text>
    <sha1>4dfa5b48d2dbd75997a5ccbf386ab358f864a750</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:Other Ultra 10 (Front).jpg</title>
  <ns>6</ns>
  <id>50</id>
  <revision>
    <id>77</id>
    <timestamp>2024-09-10T07:23:46Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22" xml:space="preserve">Other Ultra 10 (Front)</text>
    <sha1>cd92c78b5d4551567bdf0dccddedd845f43862e8</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:Ultra 10 (Rear).jpg</title>
  <ns>6</ns>
  <id>51</id>
  <revision>
    <id>78</id>
    <timestamp>2024-09-10T07:24:18Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15" xml:space="preserve">Ultra 10 (Rear)</text>
    <sha1>ef8f479a74672ef83e101ab1b4efa8179bfb9563</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:Other Ultra 10 (Rear).jpg</title>
  <ns>6</ns>
  <id>52</id>
  <revision>
    <id>79</id>
    <timestamp>2024-09-10T07:24:44Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="21" xml:space="preserve">Other Ultra 10 (Rear)</text>
    <sha1>953f6b2dfcdaffa6e722dbc2283fdae07503389c</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>Ultra 10 Workstation</title>
  <ns>0</ns>
  <id>53</id>
  <revision>
    <id>80</id>
    <timestamp>2024-09-10T07:24:57Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Another two machines I need to investigate, purchased from Re-PC at some point in 2022   '''The current state of these machines is completely unknown''' [[File:Sun Ultra 10 (front).jpg|alt=Sun Ultra 10 (front)|none|thumb|Sun Ultra 10 (front)]] [[File:Other Ultra 10 (Front).jpg|alt=Other Ultra 10 (Front)|none|thumb|Other Ultra 10 (Front)]] [[File:Ultra 10 (Rear).jpg|alt=Ultra 10 (Rear)|none|thumb|Ultra 10 (Rear)]] File:Other Ultra 10 (Rear).jpg|alt=Other Ultra 10 (Rear)..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="510" xml:space="preserve">Another two machines I need to investigate, purchased from Re-PC at some point in 2022 

'''The current state of these machines is completely unknown'''
[[File:Sun Ultra 10 (front).jpg|alt=Sun Ultra 10 (front)|none|thumb|Sun Ultra 10 (front)]]
[[File:Other Ultra 10 (Front).jpg|alt=Other Ultra 10 (Front)|none|thumb|Other Ultra 10 (Front)]]
[[File:Ultra 10 (Rear).jpg|alt=Ultra 10 (Rear)|none|thumb|Ultra 10 (Rear)]]
[[File:Other Ultra 10 (Rear).jpg|alt=Other Ultra 10 (Rear)|none|thumb|Other Ultra 10 (Rear)]]</text>
    <sha1>9fd3fb390effbe082bff15f89d4ea4b036231c8e</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>Old Computers</title>
  <ns>0</ns>
  <id>2</id>
  <revision>
    <id>81</id>
    <parentid>23</parentid>
    <timestamp>2024-09-10T07:25:55Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1170" xml:space="preserve">As the title suggests, and indeed why you're here. '''''I have a lot of old computers'''''

This page serves as an index catalog of them for easy reference.

&lt;big&gt;'''NOTE: This list is non-exhaustive as I'm constantly picking up new weird old tech'''&lt;/big&gt;


=== Acer Inc ===
[[Acer EasyStore H340]]

=== Apple Computers Inc ===
[[Powermac G4]] "Mirror Drive Door" (MDD)

[[Powermac G5]] Quad

[[eMac G4]]

[[Xserve G4]]

[[Xserve G5]]
=== Cobalt Networks ===
[[Cobalt Qube]]

[[Cobalt RaQ|Cobalt RaQ4]]

=== Dell Computers ===
[[PowerEdge 2500]]

=== Digital Equipment Corporation ===
[[DEC AlphaServer 2100|DEC AlphaServer 2100 4/275]]

=== Hewlett Packard ===
[[HP MediaSmart EX495]]

[[HP KAYAK XA 6/400 MT]]

=== Silicon Graphics ===
[[SGI Octane]]

[[SGI Visual Workstation 320]]

=== Sun Microsystems ===
[[Netra X1]]

[[Netra T1]]

[[SunFire Enterprise 420R]] 

[[Ultra 10 Workstation]]

=== Whitebox/custom builds ===

[[Windows 98 PC|World's Fastest Windows 98 PC]]

[[Disc Ripper|Disc Ripper aka "Napster"]]

=== Miscellaneous (Anything not 'retro') ===
[[Framework 13]]

[[Main Desktop]]

[[Home Server]]

[[Hyve Zeus]]

[[Hyve Cygnus]]

[[Video Capture PC]]</text>
    <sha1>47dbb1154f3550fc5a9751aed3d48823936bf404</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:98 PC (Front).jpg</title>
  <ns>6</ns>
  <id>54</id>
  <revision>
    <id>82</id>
    <timestamp>2024-09-10T07:47:28Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13" xml:space="preserve">98 PC (Front)</text>
    <sha1>84026520d5fe2a15b131ce069085b976892bf8c2</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:98 PC (Side).jpg</title>
  <ns>6</ns>
  <id>55</id>
  <revision>
    <id>83</id>
    <timestamp>2024-09-10T07:47:48Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12" xml:space="preserve">98 PC (Side)</text>
    <sha1>a81112da30e7ed420b86f093a1ae552a44464003</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:98 PC (Rear).jpg</title>
  <ns>6</ns>
  <id>56</id>
  <revision>
    <id>84</id>
    <timestamp>2024-09-10T07:48:20Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12" xml:space="preserve">98 PC (Rear)</text>
    <sha1>910685bc9053dcc5e3e116b50b5730e7d530cab9</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>Windows 98 PC</title>
  <ns>0</ns>
  <id>57</id>
  <revision>
    <id>85</id>
    <timestamp>2024-09-10T07:48:33Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "There's not much I can really add to this page that wasn't already discussed in the [https://www.youtube.com/watch?v=YETxI4rA_gs "Building the REAL "ultimate Windows 98 PC"]" video   Since I filmed that video the machine has had some (minor) upgrades  * The GTX 7800 has been replaced with a 7900 for a minor performance boost * The weird memory allocation issues have been fixed via the "SPLIT8MB" patch from Rudolph Loew * RAM has been increased from 4GB (4x1GB sticks) to..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1191" xml:space="preserve">There's not much I can really add to this page that wasn't already discussed in the [https://www.youtube.com/watch?v=YETxI4rA_gs "Building the REAL "ultimate Windows 98 PC"]" video


Since I filmed that video the machine has had some (minor) upgrades

* The GTX 7800 has been replaced with a 7900 for a minor performance boost
* The weird memory allocation issues have been fixed via the "SPLIT8MB" patch from Rudolph Loew
* RAM has been increased from 4GB (4x1GB sticks) to '''''16GB''''' (4x4GB sticks) though with the caveat that Windows 98 can only address 3.25GB of memory. Rudolph Loew's "ramdisk" patch can be utilized to add up to a 13GB RAM drive for the remaining space, but I do not have a practical reason to use this, yet
* Ethernet has been moved from a PCI based RTL 8169 to a PCI-E 1x RTL8111C. Performance is marginally improved


The machine has also been moved to a Lian Li PC-A70 case. Unfortunately the rear bay is missing and the general build quality of this case is extremely poor

[[File:98 PC (Front).jpg|none|thumb|98 PC (Front)]]
[[File:98 PC (Side).jpg|alt=98 PC (Side)|none|thumb|98 PC (Side)]]
[[File:98 PC (Rear).jpg|alt=98 PC (Rear)|none|thumb|98 PC (Rear)]]</text>
    <sha1>bdd8dbff71acb8818cbaad24174e1f3dc7c6413c</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>Disc Ripper</title>
  <ns>0</ns>
  <id>58</id>
  <revision>
    <id>86</id>
    <timestamp>2024-09-10T07:53:57Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The most recent computer I've (largely) finished building. Dubbed "Napster"   This machine is most interesting for how uninteresting it is! An i3-6100 Intel "Skylake" CPU and generic MSI motherboard with 16GB of low-speed DDR4 memory attached.   The most notable feature of this machine is what it was built for. Featuring '''''nine''''' LG BH16NS58 Blu Ray drives, this machine is able to mass-archive almost every kind of optical media CD produced.   Additional information..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="748" xml:space="preserve">The most recent computer I've (largely) finished building. Dubbed "Napster"


This machine is most interesting for how uninteresting it is! An i3-6100 Intel "Skylake" CPU and generic MSI motherboard with 16GB of low-speed DDR4 memory attached.


The most notable feature of this machine is what it was built for. Featuring '''''nine''''' LG BH16NS58 Blu Ray drives, this machine is able to mass-archive almost every kind of optical media CD produced.


Additional information about this machines ripping capability can be inferred from the "[https://github.com/saramibreak/DiscImageCreator DiscImageCreator]" Github repository but the tl;dr is this machine is built to create '''''Redump quality''''' disc images of computer software CD's and games</text>
    <sha1>5ae408780a710677859c9cd96972876f17b8740c</sha1>
  </revision>
  <revision>
    <id>87</id>
    <parentid>86</parentid>
    <timestamp>2024-09-10T07:54:18Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="766" xml:space="preserve">The most recent computer I've (largely) finished building. Affectionately nicknamed "Napster"


This machine is most interesting for how uninteresting it is! An i3-6100 Intel "Skylake" CPU and generic MSI motherboard with 16GB of low-speed DDR4 memory attached.


The most notable feature of this machine is what it was built for. Featuring '''''nine''''' LG BH16NS58 Blu Ray drives, this machine is able to mass-archive almost every kind of optical media CD produced.


Additional information about this machines ripping capability can be inferred from the "[https://github.com/saramibreak/DiscImageCreator DiscImageCreator]" Github repository but the tl;dr is this machine is built to create '''''Redump quality''''' disc images of computer software CD's and games</text>
    <sha1>54a6c1b03584b121dbd7887cd0cea708d826c3d2</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:Hyve Cygnus (Front).jpg</title>
  <ns>6</ns>
  <id>59</id>
  <revision>
    <id>88</id>
    <timestamp>2024-09-10T07:58:47Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19" xml:space="preserve">Hyve Cygnus (Front)</text>
    <sha1>5910323b37ea3d5b2c9dd625d0513e6091d469e8</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>Hyve Cygnus</title>
  <ns>0</ns>
  <id>60</id>
  <revision>
    <id>89</id>
    <timestamp>2024-09-10T07:58:57Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The Hyve "Cygnus" is another ex-whitebox-built-for-Facebook en masse server   Unlike the [[Hyve Zeus]] the Cygnus was built for disk storage. As such it's capable of supporting '''''ten 3.5" hard disks''''' via its extremely long 1U chassis    My unit was graciously gifted by [https://social.sdf.org/@indrora Indrora of SDF fame] and originally dubbed "The Compensator"    At this time the unit is not in use, however it is otherwise stock configuration of a Hyve Cygnus ser..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="568" xml:space="preserve">The Hyve "Cygnus" is another ex-whitebox-built-for-Facebook en masse server


Unlike the [[Hyve Zeus]] the Cygnus was built for disk storage. As such it's capable of supporting '''''ten 3.5" hard disks''''' via its extremely long 1U chassis 


My unit was graciously gifted by [https://social.sdf.org/@indrora Indrora of SDF fame] and originally dubbed "The Compensator" 


At this time the unit is not in use, however it is otherwise stock configuration of a Hyve Cygnus server.

[[File:Hyve Cygnus (Front).jpg|alt=Hyve Cygnus (Front)|none|thumb|Hyve Cygnus (Front)]]</text>
    <sha1>b2ab6a6ee4caf56c24149ba8bb3c3a684f0afb9b</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>Hyve Zeus</title>
  <ns>0</ns>
  <id>7</id>
  <revision>
    <id>90</id>
    <parentid>22</parentid>
    <timestamp>2024-12-16T02:47:22Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="765" xml:space="preserve">The Hyve "Zeus" is a server made for Facebook before their "Open Compute Project". As a result there's about a bajillion of these things floating around on eBay these days


Hyve Zeus units feature a Super Micro X9DRD-iF motherboard with all PCI-E slots except for one removed


They are usually equipped with some variation of low-end Intel Xeons with passively cooled heatsinks attached


The unit I (unfortunately) upgraded with two top-end Xeon 2697v2's and 128GB of DDR3 ECC memory. As a result the unit now contains two Delta R25 7K RPM fans. The resulting noise of this server renders it virtually unusable in areas with people present 


'''It is presently part of the infrastructure of my local hackerspace. However we are likely to retire it in future'''</text>
    <sha1>cde867a8176a62d1ccc3610a90734fdf0f194335</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>Compu-Global-Hyper-Mega-Net</title>
  <ns>0</ns>
  <id>61</id>
  <revision>
    <id>91</id>
    <timestamp>2025-01-17T20:38:49Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have an..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2171" xml:space="preserve">Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in its embryonic stages as I step through the trial-by-fire of the reality of setting up 1990's era telecommunications infrastructure in a way that is both functional and not inconvenient for myself or others in the space it is physically housed in.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "fun" for us!


A longer term goal includes providing democratized access for users to begin submitting their own projects and content ala [[wikipedia:GeoCities|Geocities]] and setting up federated networking with other retro computing users, similar to GlobalTalk but with a larger scope of features and functionality</text>
    <sha1>d24167fa524a7eb22c0c5b32be92617d27069326</sha1>
  </revision>
  <revision>
    <id>92</id>
    <parentid>91</parentid>
    <timestamp>2025-01-17T20:44:20Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2485" xml:space="preserve">Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in its embryonic stages as I step through the trial-by-fire of the reality of setting up 1990's era telecommunications infrastructure in a way that is both functional and not inconvenient for myself or others in the space it is physically housed in.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "fun" for us!


A longer term goal includes providing democratized access for users to begin submitting their own projects and content ala [[wikipedia:GeoCities|Geocities]] and setting up federated networking with other retro computing users, similar to GlobalTalk but with a larger scope of features and functionality

== '''As an additional project, folks are being recruited to help set up infrastructure and services to run on CGHMN once it launches officially. If you have services you would like to help get running on this vintage intranet, [https://social.restless.systems/@CursedSilicon please reach out via Mastodon]''' ==</text>
    <sha1>e7ca5a5a77a5840e9d314670d448e0f7440dfb6f</sha1>
  </revision>
  <revision>
    <id>93</id>
    <parentid>92</parentid>
    <timestamp>2025-01-17T21:44:35Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2652" xml:space="preserve">Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in its embryonic stages as I step through the trial-by-fire of the reality of setting up 1990's era telecommunications infrastructure in a way that is both functional and not inconvenient for myself or others in the space it is physically housed in.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "fun" for us!


A longer term goal includes providing democratized access for users to begin submitting their own projects and content ala [[wikipedia:GeoCities|Geocities]] and setting up federated networking with other retro computing users, similar to GlobalTalk but with a larger scope of features and functionality

== '''As an additional project, folks are being recruited to help set up infrastructure and services to run on CGHMN once it launches officially. If you have services you would like to help get running on this vintage intranet, [https://social.restless.systems/@CursedSilicon please reach out via Mastodon]''' ==

=== Currently we need mainly retro sysadmins, web developers/designers and networking folks. Hardware (and hosting) is doable, we just need stuff to *run* on it! ===</text>
    <sha1>8556fd0a697b0d2e57d6d5e44bcb8da311eda818</sha1>
  </revision>
  <revision>
    <id>94</id>
    <parentid>93</parentid>
    <timestamp>2025-01-20T23:43:28Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5591" xml:space="preserve">Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in its embryonic stages as I step through the trial-by-fire of the reality of setting up 1990's era telecommunications infrastructure in a way that is both functional and not inconvenient for myself or others in the space it is physically housed in.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "fun" for us!


A longer term goal includes providing democratized access for users to begin submitting their own projects and content ala [[wikipedia:GeoCities|Geocities]] and setting up federated networking with other retro computing users, similar to GlobalTalk but with a larger scope of features and functionality


= '''Currently we're looking to recruit volunteers for Sysadmin/Sysop, building websites (think Geocities), running old game servers and other software, network engineers and anyone and everyone who has the technical capability to help out and volunteer their time. Donations to fund the network are also welcome but are entirely optional. If you would like to do either [https://social.restless.systems/@CursedSilicon please reach out via Mastodon]''' =


=== So what's this all about? ===


CGHMN is a collaborative project aimed to create a late 1990's/early 2000's compatible "internet" for retro computing enthusiasts and their machines

=== Okay so how do I connect to it? ===


We're currently exploring the best way(s) to allow users to connect their machines to the network. Our intention is to provide as varied a list of options as possible. Current outlined methods under investigation are

* '''Real V.92 Dial-Up service'''. Pending the ability to acquire a [[wikipedia:Primary_Rate_Interface|PRI line]] we would be able to provide dial-in services via a 425 or 206 area code phone number. This service would likely be limited to 24 concurrent users and would be shared with VoIP users
* '''Dial-In via VoIP'''. A user on Mastodon has claimed to have successfully run Dial-Up service over VoIP even with an international connection from China to South America. This needs to be explored further
* '''Ethernet tunneling/emulation'''. Similar to how early DOCSIS Cable modems worked with just an ethernet jack on the rear of the device and DHCP. Users can purchase an '''''OpenWRT compatible''''' device such as a Raspberry Pi (any model) or a [https://store-us.gl-inet.com/products/us-local-delivery-shadow-mini-smart-router-powerful-wireless-performance-travel-wifi-gl-ar300m16 GL-AR300M16] and then connect to the network. A network switch can be optionally used to connect multiple devices in parallel, or a router may be preferable in order to add NAT functionality and prevent local network services (such as DHCP) from "leaking" back out into the wider network.

=== How fast is it? ===


Total internal network capacity is '''''1Gbps''''' (symmetric) due to limitations of the switches in operation. This speed may be raised or lowered depending on future federation with other members. 

Current plans are to offer V.92 (56Kbps), DSL (1Mbps/256K) and T1 (1.5Mbps symmetric) services.

An optional donation tier may be added (either 10Mbps or 100Mbps) for users who want to financially support the network (costs of electricity, server upkeep and other factors)

=== Is this safe to use? I thought connecting old PC's to the internet was a bad idea! ===


Compu-Global-Hyper-Mega-Net is not accessible by the wider internet and is specifically designed to be a ''hermetically sealed'' network. Users can only connect via the above methods '''and can only communicate with other devices on the network'''. Users that violate the Terms of Service or attempt to abuse the network (or other members) will have their access '''permanently removed'''. With that said the usual rules about not downloading suspicious files and other "internet hygiene" rules still apply. While we don't expect bad actors to be a problem, please ensure that any files contributed to the network are scanned for malware first! [https://www.virustotal.com/gui/home/upload VirusTotal] provides free scanning services for this.</text>
    <sha1>d6ec8f8fc662d6e7e0b26ec4bbf5505c17832b4b</sha1>
  </revision>
  <revision>
    <id>95</id>
    <parentid>94</parentid>
    <timestamp>2025-01-20T23:43:45Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>/* Currently we're looking to recruit volunteers for Sysadmin/Sysop, building websites (think Geocities), running old game servers and other software, network engineers and anyone and everyone who has the technical capability to help out and volun */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5617" xml:space="preserve">Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in its embryonic stages as I step through the trial-by-fire of the reality of setting up 1990's era telecommunications infrastructure in a way that is both functional and not inconvenient for myself or others in the space it is physically housed in.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "fun" for us!


A longer term goal includes providing democratized access for users to begin submitting their own projects and content ala [[wikipedia:GeoCities|Geocities]] and setting up federated networking with other retro computing users, similar to GlobalTalk but with a larger scope of features and functionality


&lt;blockquote&gt;
= '''Currently we're looking to recruit volunteers for Sysadmin/Sysop, building websites (think Geocities), running old game servers and other software, network engineers and anyone and everyone who has the technical capability to help out and volunteer their time. Donations to fund the network are also welcome but are entirely optional. If you would like to do either [https://social.restless.systems/@CursedSilicon please reach out via Mastodon]''' =
&lt;/blockquote&gt;

=== So what's this all about? ===


CGHMN is a collaborative project aimed to create a late 1990's/early 2000's compatible "internet" for retro computing enthusiasts and their machines

=== Okay so how do I connect to it? ===


We're currently exploring the best way(s) to allow users to connect their machines to the network. Our intention is to provide as varied a list of options as possible. Current outlined methods under investigation are

* '''Real V.92 Dial-Up service'''. Pending the ability to acquire a [[wikipedia:Primary_Rate_Interface|PRI line]] we would be able to provide dial-in services via a 425 or 206 area code phone number. This service would likely be limited to 24 concurrent users and would be shared with VoIP users
* '''Dial-In via VoIP'''. A user on Mastodon has claimed to have successfully run Dial-Up service over VoIP even with an international connection from China to South America. This needs to be explored further
* '''Ethernet tunneling/emulation'''. Similar to how early DOCSIS Cable modems worked with just an ethernet jack on the rear of the device and DHCP. Users can purchase an '''''OpenWRT compatible''''' device such as a Raspberry Pi (any model) or a [https://store-us.gl-inet.com/products/us-local-delivery-shadow-mini-smart-router-powerful-wireless-performance-travel-wifi-gl-ar300m16 GL-AR300M16] and then connect to the network. A network switch can be optionally used to connect multiple devices in parallel, or a router may be preferable in order to add NAT functionality and prevent local network services (such as DHCP) from "leaking" back out into the wider network.

=== How fast is it? ===


Total internal network capacity is '''''1Gbps''''' (symmetric) due to limitations of the switches in operation. This speed may be raised or lowered depending on future federation with other members. 

Current plans are to offer V.92 (56Kbps), DSL (1Mbps/256K) and T1 (1.5Mbps symmetric) services.

An optional donation tier may be added (either 10Mbps or 100Mbps) for users who want to financially support the network (costs of electricity, server upkeep and other factors)

=== Is this safe to use? I thought connecting old PC's to the internet was a bad idea! ===


Compu-Global-Hyper-Mega-Net is not accessible by the wider internet and is specifically designed to be a ''hermetically sealed'' network. Users can only connect via the above methods '''and can only communicate with other devices on the network'''. Users that violate the Terms of Service or attempt to abuse the network (or other members) will have their access '''permanently removed'''. With that said the usual rules about not downloading suspicious files and other "internet hygiene" rules still apply. While we don't expect bad actors to be a problem, please ensure that any files contributed to the network are scanned for malware first! [https://www.virustotal.com/gui/home/upload VirusTotal] provides free scanning services for this.</text>
    <sha1>4ae488e4d833015adbe51116da9e086e5494ae95</sha1>
  </revision>
  <revision>
    <id>96</id>
    <parentid>95</parentid>
    <timestamp>2025-01-20T23:44:06Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5634" xml:space="preserve">=== Preamble ===
Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in its embryonic stages as I step through the trial-by-fire of the reality of setting up 1990's era telecommunications infrastructure in a way that is both functional and not inconvenient for myself or others in the space it is physically housed in.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "fun" for us!


A longer term goal includes providing democratized access for users to begin submitting their own projects and content ala [[wikipedia:GeoCities|Geocities]] and setting up federated networking with other retro computing users, similar to GlobalTalk but with a larger scope of features and functionality


&lt;blockquote&gt;
= '''Currently we're looking to recruit volunteers for Sysadmin/Sysop, building websites (think Geocities), running old game servers and other software, network engineers and anyone and everyone who has the technical capability to help out and volunteer their time. Donations to fund the network are also welcome but are entirely optional. If you would like to do either [https://social.restless.systems/@CursedSilicon please reach out via Mastodon]''' =
&lt;/blockquote&gt;

=== So what's this all about? ===


CGHMN is a collaborative project aimed to create a late 1990's/early 2000's compatible "internet" for retro computing enthusiasts and their machines

=== Okay so how do I connect to it? ===


We're currently exploring the best way(s) to allow users to connect their machines to the network. Our intention is to provide as varied a list of options as possible. Current outlined methods under investigation are

* '''Real V.92 Dial-Up service'''. Pending the ability to acquire a [[wikipedia:Primary_Rate_Interface|PRI line]] we would be able to provide dial-in services via a 425 or 206 area code phone number. This service would likely be limited to 24 concurrent users and would be shared with VoIP users
* '''Dial-In via VoIP'''. A user on Mastodon has claimed to have successfully run Dial-Up service over VoIP even with an international connection from China to South America. This needs to be explored further
* '''Ethernet tunneling/emulation'''. Similar to how early DOCSIS Cable modems worked with just an ethernet jack on the rear of the device and DHCP. Users can purchase an '''''OpenWRT compatible''''' device such as a Raspberry Pi (any model) or a [https://store-us.gl-inet.com/products/us-local-delivery-shadow-mini-smart-router-powerful-wireless-performance-travel-wifi-gl-ar300m16 GL-AR300M16] and then connect to the network. A network switch can be optionally used to connect multiple devices in parallel, or a router may be preferable in order to add NAT functionality and prevent local network services (such as DHCP) from "leaking" back out into the wider network.

=== How fast is it? ===


Total internal network capacity is '''''1Gbps''''' (symmetric) due to limitations of the switches in operation. This speed may be raised or lowered depending on future federation with other members. 

Current plans are to offer V.92 (56Kbps), DSL (1Mbps/256K) and T1 (1.5Mbps symmetric) services.

An optional donation tier may be added (either 10Mbps or 100Mbps) for users who want to financially support the network (costs of electricity, server upkeep and other factors)

=== Is this safe to use? I thought connecting old PC's to the internet was a bad idea! ===


Compu-Global-Hyper-Mega-Net is not accessible by the wider internet and is specifically designed to be a ''hermetically sealed'' network. Users can only connect via the above methods '''and can only communicate with other devices on the network'''. Users that violate the Terms of Service or attempt to abuse the network (or other members) will have their access '''permanently removed'''. With that said the usual rules about not downloading suspicious files and other "internet hygiene" rules still apply. While we don't expect bad actors to be a problem, please ensure that any files contributed to the network are scanned for malware first! [https://www.virustotal.com/gui/home/upload VirusTotal] provides free scanning services for this.</text>
    <sha1>8ab8c4c2d76433e990918bb7361340d63f632e33</sha1>
  </revision>
  <revision>
    <id>97</id>
    <parentid>96</parentid>
    <timestamp>2025-01-20T23:44:27Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5601" xml:space="preserve">=== Preamble ===
Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in its embryonic stages as I step through the trial-by-fire of the reality of setting up 1990's era telecommunications infrastructure in a way that is both functional and not inconvenient for myself or others in the space it is physically housed in.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "fun" for us!


A longer term goal includes providing democratized access for users to begin submitting their own projects and content ala [[wikipedia:GeoCities|Geocities]] and setting up federated networking with other retro computing users, similar to GlobalTalk but with a larger scope of features and functionality
=== So what's this all about? ===


CGHMN is a collaborative project aimed to create a late 1990's/early 2000's compatible "internet" for retro computing enthusiasts and their machines

=== Okay so how do I connect to it? ===


We're currently exploring the best way(s) to allow users to connect their machines to the network. Our intention is to provide as varied a list of options as possible. Current outlined methods under investigation are

* '''Real V.92 Dial-Up service'''. Pending the ability to acquire a [[wikipedia:Primary_Rate_Interface|PRI line]] we would be able to provide dial-in services via a 425 or 206 area code phone number. This service would likely be limited to 24 concurrent users and would be shared with VoIP users
* '''Dial-In via VoIP'''. A user on Mastodon has claimed to have successfully run Dial-Up service over VoIP even with an international connection from China to South America. This needs to be explored further
* '''Ethernet tunneling/emulation'''. Similar to how early DOCSIS Cable modems worked with just an ethernet jack on the rear of the device and DHCP. Users can purchase an '''''OpenWRT compatible''''' device such as a Raspberry Pi (any model) or a [https://store-us.gl-inet.com/products/us-local-delivery-shadow-mini-smart-router-powerful-wireless-performance-travel-wifi-gl-ar300m16 GL-AR300M16] and then connect to the network. A network switch can be optionally used to connect multiple devices in parallel, or a router may be preferable in order to add NAT functionality and prevent local network services (such as DHCP) from "leaking" back out into the wider network.

=== How fast is it? ===


Total internal network capacity is '''''1Gbps''''' (symmetric) due to limitations of the switches in operation. This speed may be raised or lowered depending on future federation with other members. 

Current plans are to offer V.92 (56Kbps), DSL (1Mbps/256K) and T1 (1.5Mbps symmetric) services.

An optional donation tier may be added (either 10Mbps or 100Mbps) for users who want to financially support the network (costs of electricity, server upkeep and other factors)

=== Is this safe to use? I thought connecting old PC's to the internet was a bad idea! ===


Compu-Global-Hyper-Mega-Net is not accessible by the wider internet and is specifically designed to be a ''hermetically sealed'' network. Users can only connect via the above methods '''and can only communicate with other devices on the network'''. Users that violate the Terms of Service or attempt to abuse the network (or other members) will have their access '''permanently removed'''. With that said the usual rules about not downloading suspicious files and other "internet hygiene" rules still apply. While we don't expect bad actors to be a problem, please ensure that any files contributed to the network are scanned for malware first! [https://www.virustotal.com/gui/home/upload VirusTotal] provides free scanning services for this.

'''Currently we're looking to recruit volunteers for Sysadmin/Sysop, building websites (think Geocities), running old game servers and other software, network engineers and anyone and everyone who has the technical capability to help out and volunteer their time. Donations to fund the network are also welcome but are entirely optional. If you would like to do either [https://social.restless.systems/@CursedSilicon please reach out via Mastodon]'''</text>
    <sha1>3474e7ada94e4af02a6ec2b6d45cc8b74b6d6132</sha1>
  </revision>
  <revision>
    <id>98</id>
    <parentid>97</parentid>
    <timestamp>2025-01-20T23:44:50Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5612" xml:space="preserve">=== Preamble ===
Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in its embryonic stages as I step through the trial-by-fire of the reality of setting up 1990's era telecommunications infrastructure in a way that is both functional and not inconvenient for myself or others in the space it is physically housed in.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "fun" for us!


A longer term goal includes providing democratized access for users to begin submitting their own projects and content ala [[wikipedia:GeoCities|Geocities]] and setting up federated networking with other retro computing users, similar to GlobalTalk but with a larger scope of features and functionality
=== So what's this all about? ===


CGHMN is a collaborative project aimed to create a late 1990's/early 2000's compatible "internet" for retro computing enthusiasts and their machines

=== Okay so how do I connect to it? ===


We're currently exploring the best way(s) to allow users to connect their machines to the network. Our intention is to provide as varied a list of options as possible. Current outlined methods under investigation are

* '''Real V.92 Dial-Up service'''. Pending the ability to acquire a [[wikipedia:Primary_Rate_Interface|PRI line]] we would be able to provide dial-in services via a 425 or 206 area code phone number. This service would likely be limited to 24 concurrent users and would be shared with VoIP users
* '''Dial-In via VoIP'''. A user on Mastodon has claimed to have successfully run Dial-Up service over VoIP even with an international connection from China to South America. This needs to be explored further
* '''Ethernet tunneling/emulation'''. Similar to how early DOCSIS Cable modems worked with just an ethernet jack on the rear of the device and DHCP. Users can purchase an '''''OpenWRT compatible''''' device such as a Raspberry Pi (any model) or a [https://store-us.gl-inet.com/products/us-local-delivery-shadow-mini-smart-router-powerful-wireless-performance-travel-wifi-gl-ar300m16 GL-AR300M16] and then connect to the network. A network switch can be optionally used to connect multiple devices in parallel, or a router may be preferable in order to add NAT functionality and prevent local network services (such as DHCP) from "leaking" back out into the wider network.

=== How fast is it? ===


Total internal network capacity is '''''1Gbps''''' (symmetric) due to limitations of the switches in operation. This speed may be raised or lowered depending on future federation with other members. 

Current plans are to offer V.92 (56Kbps), DSL (1Mbps/256K) and T1 (1.5Mbps symmetric) services.

An optional donation tier may be added (either 10Mbps or 100Mbps) for users who want to financially support the network (costs of electricity, server upkeep and other factors)

=== Is this safe to use? I thought connecting old PC's to the internet was a bad idea! ===


Compu-Global-Hyper-Mega-Net is not accessible by the wider internet and is specifically designed to be a ''hermetically sealed'' network. Users can only connect via the above methods '''and can only communicate with other devices on the network'''. Users that violate the Terms of Service or attempt to abuse the network (or other members) will have their access '''permanently removed'''. With that said the usual rules about not downloading suspicious files and other "internet hygiene" rules still apply. While we don't expect bad actors to be a problem, please ensure that any files contributed to the network are scanned for malware first! [https://www.virustotal.com/gui/home/upload VirusTotal] provides free scanning services for this.

'''&lt;big&gt;Currently we're looking to recruit volunteers for Sysadmin/Sysop, building websites (think Geocities), running old game servers and other software, network engineers and anyone and everyone who has the technical capability to help out and volunteer their time. Donations to fund the network are also welcome but are entirely optional. If you would like to do either [https://social.restless.systems/@CursedSilicon please reach out via Mastodon]&lt;/big&gt;'''</text>
    <sha1>824f97a16b022cc868c60aae13bd5950a792d136</sha1>
  </revision>
  <revision>
    <id>99</id>
    <parentid>98</parentid>
    <timestamp>2025-01-20T23:45:14Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5637" xml:space="preserve">=== Preamble ===
Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in its embryonic stages as I step through the trial-by-fire of the reality of setting up 1990's era telecommunications infrastructure in a way that is both functional and not inconvenient for myself or others in the space it is physically housed in.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "fun" for us!


A longer term goal includes providing democratized access for users to begin submitting their own projects and content ala [[wikipedia:GeoCities|Geocities]] and setting up federated networking with other retro computing users, similar to GlobalTalk but with a larger scope of features and functionality
=== So what's this all about? ===


CGHMN is a collaborative project aimed to create a late 1990's/early 2000's compatible "internet" for retro computing enthusiasts and their machines

=== Okay so how do I connect to it? ===


We're currently exploring the best way(s) to allow users to connect their machines to the network. Our intention is to provide as varied a list of options as possible. Current outlined methods under investigation are

* '''Real V.92 Dial-Up service'''. Pending the ability to acquire a [[wikipedia:Primary_Rate_Interface|PRI line]] we would be able to provide dial-in services via a 425 or 206 area code phone number. This service would likely be limited to 24 concurrent users and would be shared with VoIP users
* '''Dial-In via VoIP'''. A user on Mastodon has claimed to have successfully run Dial-Up service over VoIP even with an international connection from China to South America. This needs to be explored further
* '''Ethernet tunneling/emulation'''. Similar to how early DOCSIS Cable modems worked with just an ethernet jack on the rear of the device and DHCP. Users can purchase an '''''OpenWRT compatible''''' device such as a Raspberry Pi (any model) or a [https://store-us.gl-inet.com/products/us-local-delivery-shadow-mini-smart-router-powerful-wireless-performance-travel-wifi-gl-ar300m16 GL-AR300M16] and then connect to the network. A network switch can be optionally used to connect multiple devices in parallel, or a router may be preferable in order to add NAT functionality and prevent local network services (such as DHCP) from "leaking" back out into the wider network.

=== How fast is it? ===


Total internal network capacity is '''''1Gbps''''' (symmetric) due to limitations of the switches in operation. This speed may be raised or lowered depending on future federation with other members. 

Current plans are to offer V.92 (56Kbps), DSL (1Mbps/256K) and T1 (1.5Mbps symmetric) services.

An optional donation tier may be added (either 10Mbps or 100Mbps) for users who want to financially support the network (costs of electricity, server upkeep and other factors)

=== Is this safe to use? I thought connecting old PC's to the internet was a bad idea! ===


Compu-Global-Hyper-Mega-Net is not accessible by the wider internet and is specifically designed to be a ''hermetically sealed'' network. Users can only connect via the above methods '''and can only communicate with other devices on the network'''. Users that violate the Terms of Service or attempt to abuse the network (or other members) will have their access '''permanently removed'''. With that said the usual rules about not downloading suspicious files and other "internet hygiene" rules still apply. While we don't expect bad actors to be a problem, please ensure that any files contributed to the network are scanned for malware first! [https://www.virustotal.com/gui/home/upload VirusTotal] provides free scanning services for this.

&lt;blockquote&gt;'''&lt;big&gt;Currently we're looking to recruit volunteers for Sysadmin/Sysop, building websites (think Geocities), running old game servers and other software, network engineers and anyone and everyone who has the technical capability to help out and volunteer their time. Donations to fund the network are also welcome but are entirely optional. If you would like to do either [https://social.restless.systems/@CursedSilicon please reach out via Mastodon]&lt;/big&gt;'''&lt;/blockquote&gt;</text>
    <sha1>c3ae65d5f4d6109438880899e492339b3ff9330c</sha1>
  </revision>
  <revision>
    <id>100</id>
    <parentid>99</parentid>
    <timestamp>2025-01-29T15:40:50Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5807" xml:space="preserve">=== Preamble ===
Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in its embryonic stages as I step through the trial-by-fire of the reality of setting up 1990's era telecommunications infrastructure in a way that is both functional and not inconvenient for myself or others in the space it is physically housed in.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "fun" for us!


A longer term goal includes providing democratized access for users to begin submitting their own projects and content ala [[wikipedia:GeoCities|Geocities]] and setting up federated networking with other retro computing users, similar to GlobalTalk but with a larger scope of features and functionality
=== So what's this all about? ===


CGHMN is a collaborative project aimed to create a late 1990's/early 2000's compatible "internet" for retro computing enthusiasts and their machines

=== Okay so how do I connect to it? ===


We're currently exploring the best way(s) to allow users to connect their machines to the network. Our intention is to provide as varied a list of options as possible. Current outlined methods under investigation are

* '''Real V.92 Dial-Up service'''. Pending the ability to acquire a [[wikipedia:Primary_Rate_Interface|PRI line]] we would be able to provide dial-in services via a 425 or 206 area code phone number. This service would likely be limited to 24 concurrent users and would be shared with VoIP users
* '''Dial-In via VoIP'''. A user on Mastodon has claimed to have successfully run Dial-Up service over VoIP even with an international connection from China to South America. This needs to be explored further
* '''Ethernet tunneling/emulation'''. Similar to how early DOCSIS Cable modems worked with just an ethernet jack on the rear of the device and DHCP. Users can purchase an '''''OpenWRT compatible''''' device such as a Raspberry Pi (any model) or a [https://store-us.gl-inet.com/products/us-local-delivery-shadow-mini-smart-router-powerful-wireless-performance-travel-wifi-gl-ar300m16 GL-AR300M16] and then connect to the network. A network switch can be optionally used to connect multiple devices in parallel, or a router may be preferable in order to add NAT functionality and prevent local network services (such as DHCP) from "leaking" back out into the wider network.

=== How fast is it? ===


Total internal network capacity is '''''1Gbps''''' (symmetric) due to limitations of the switches in operation. This speed may be raised or lowered depending on future federation with other members. 

Current plans are to offer V.92 (56Kbps), DSL (1Mbps/256K) and T1 (1.5Mbps symmetric) services.

An optional donation tier may be added (either 10Mbps or 100Mbps) for users who want to financially support the network (costs of electricity, server upkeep and other factors)

=== Is this safe to use? I thought connecting old PC's to the internet was a bad idea! ===


Compu-Global-Hyper-Mega-Net is not accessible by the wider internet and is specifically designed to be a ''hermetically sealed'' network. Users can only connect via the above methods '''and can only communicate with other devices on the network'''. Users that violate the Terms of Service or attempt to abuse the network (or other members) will have their access '''permanently removed'''. With that said the usual rules about not downloading suspicious files and other "internet hygiene" rules still apply. While we don't expect bad actors to be a problem, please ensure that any files contributed to the network are scanned for malware first! [https://www.virustotal.com/gui/home/upload VirusTotal] provides free scanning services for this.

=== How can I help? ===


A lot of folks have offered to donate server hosting which is wonderful. Though not (yet!) required. The two biggest things we need are 


'''Donations to buy infrastructure''' (Particularly hard disks!) there's an Amazon Wishlist here that will get updated over time. https://www.amazon.com/hz/wishlist/ls/1W3S0E9IN7ZB7?ref_=wl_share


'''Volunteers who want to set up services'''. Once we've got the servers set up and running, well, we need '''''stuff''''' to run on them. Wanna make a 90's website or run a server for some old game you like? Get in touch via Mastodon, [https://discord.gg/scMGtSnx5c or via the Discord server]</text>
    <sha1>20a650667832229cfb745e828c594240f52510fd</sha1>
  </revision>
  <revision>
    <id>101</id>
    <parentid>100</parentid>
    <timestamp>2025-01-29T17:59:36Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5856" xml:space="preserve">=== Preamble ===
Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in its embryonic stages as I step through the trial-by-fire of the reality of setting up 1990's era telecommunications infrastructure in a way that is both functional and not inconvenient for myself or others in the space it is physically housed in.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "fun" for us!


A longer term goal includes providing democratized access for users to begin submitting their own projects and content ala [[wikipedia:GeoCities|Geocities]] and setting up federated networking with other retro computing users, similar to GlobalTalk but with a larger scope of features and functionality
=== So what's this all about? ===


CGHMN is a collaborative project aimed to create a late 1990's/early 2000's compatible "internet" for retro computing enthusiasts and their machines

=== Okay so how do I connect to it? ===


We're currently exploring the best way(s) to allow users to connect their machines to the network. Our intention is to provide as varied a list of options as possible. Current outlined methods under investigation are

* '''Real V.92 Dial-Up service'''. Pending the ability to acquire a [[wikipedia:Primary_Rate_Interface|PRI line]] we would be able to provide dial-in services via a 425 or 206 area code phone number. This service would likely be limited to 24 concurrent users and would be shared with VoIP users
* '''Dial-In via VoIP'''. A user on Mastodon has claimed to have successfully run Dial-Up service over VoIP even with an international connection from China to South America. This needs to be explored further
* '''Ethernet tunneling/emulation'''. Similar to how early DOCSIS Cable modems worked with just an ethernet jack on the rear of the device and DHCP. Users can purchase an '''''OpenWRT compatible''''' device such as a Raspberry Pi (any model) or a [https://store-us.gl-inet.com/products/us-local-delivery-shadow-mini-smart-router-powerful-wireless-performance-travel-wifi-gl-ar300m16 GL-AR300M16] and then connect to the network. A network switch can be optionally used to connect multiple devices in parallel, or a router may be preferable in order to add NAT functionality and prevent local network services (such as DHCP) from "leaking" back out into the wider network.

=== How fast is it? ===


Total internal network capacity is '''''1Gbps''''' (symmetric) due to limitations of the switches in operation. This speed may be raised or lowered depending on future federation with other members. 

Current plans are to offer V.92 (56Kbps), DSL (1Mbps/256K) and T1 (1.5Mbps symmetric) services.

An optional donation tier may be added (either 10Mbps or 100Mbps) for users who want to financially support the network (costs of electricity, server upkeep and other factors)

=== Is this safe to use? I thought connecting old PC's to the internet was a bad idea! ===


Compu-Global-Hyper-Mega-Net is not accessible by the wider internet and is specifically designed to be a ''hermetically sealed'' network. Users can only connect via the above methods '''and can only communicate with other devices on the network'''. Users that violate the Terms of Service or attempt to abuse the network (or other members) will have their access '''permanently removed'''. With that said the usual rules about not downloading suspicious files and other "internet hygiene" rules still apply. While we don't expect bad actors to be a problem, please ensure that any files contributed to the network are scanned for malware first! [https://www.virustotal.com/gui/home/upload VirusTotal] provides free scanning services for this.

=== How can I help? ===


A lot of folks have offered to donate server hosting which is wonderful. Though not (yet!) required. The two biggest things we need are 


'''Donations to buy infrastructure''' (Particularly hard disks!) there's an Amazon Wishlist here that will get updated over time. https://www.amazon.com/hz/wishlist/ls/1W3S0E9IN7ZB7?ref_=wl_share


'''Volunteers who want to set up services'''. Once we've got the servers set up and running, well, we need '''''stuff''''' to run on them. Wanna make a 90's website or run a server for some old game you like? Get in touch [https://social.restless.systems/@CursedSilicon via Mastodon], [https://discord.gg/scMGtSnx5c or via the Discord server]</text>
    <sha1>98c7b2ff81774041774beabb759823608c77cbbe</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:PXL 20250214 033500161.jpg</title>
  <ns>6</ns>
  <id>62</id>
  <revision>
    <id>102</id>
    <timestamp>2025-02-14T23:08:34Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20" xml:space="preserve">XPS Pro 200N (front)</text>
    <sha1>063492bfd1852f0412c3edb4caebdf296f001970</sha1>
  </revision>
</page>
<page arvcontinue="20240907090025|52">
  <title>File:PXL 20250214 033516741.jpg</title>
  <ns>6</ns>
  <id>63</id>
  <revision>
    <id>103</id>
    <timestamp>2025-02-14T23:08:53Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19" xml:space="preserve">XPS Pro 200N (rear)</text>
    <sha1>6b5a3915cd39ec43e3ee678179b5da28fa5f43c3</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>Dell XPS Pro200N</title>
  <ns>0</ns>
  <id>64</id>
  <revision>
    <id>104</id>
    <timestamp>2025-02-14T23:09:52Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Recent pickup from a University of Washington (UW) auction.   Reading online this unit seems to be equipped with a 200Mhz(!) Pentium Pro processor  The amount of RAM has not been directly tested, but according to the part number MT18LD1672G-6X may be 128MB (the max supported by the motherboard)  At this time the machine does not (yet) have any uses. The Pentium Pro performs poorly with 16-bit code which makes running Windows 3.1 or 95 on it undesirable  Early Linux may a..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="883" xml:space="preserve">Recent pickup from a University of Washington (UW) auction. 

Reading online this unit seems to be equipped with a 200Mhz(!) Pentium Pro processor

The amount of RAM has not been directly tested, but according to the part number MT18LD1672G-6X may be 128MB (the max supported by the motherboard)

At this time the machine does not (yet) have any uses. The Pentium Pro performs poorly with 16-bit code which makes running Windows 3.1 or 95 on it undesirable

Early Linux may also be an option for this device as emulation via 86box is ''difficult''


Images of this device also show several (unknown) expansion cards from what ever it was being used for originally. These have been removed after photographing

[[File:PXL 20250214 033500161.jpg|thumb|alt=XPS Pro 200N (front)|XPS Pro 200N (front)]]
[[File:PXL 20250214 033516741.jpg|thumb|alt=XPS Pro 200N (rear)|XPS Pro 200N (rear)]]</text>
    <sha1>112c42448ddfdbe4d0535e61e28dd3f43c47de44</sha1>
  </revision>
  <revision>
    <id>108</id>
    <parentid>104</parentid>
    <timestamp>2025-02-17T18:28:40Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Thumbnails unfucked?</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="882" xml:space="preserve">Recent pickup from a University of Washington (UW) auction. 

Reading online this unit seems to be equipped with a 200Mhz(!) Pentium Pro processor

The amount of RAM has not been directly tested, but according to the part number MT18LD1672G-6X may be 128MB (the max supported by the motherboard)

At this time the machine does not (yet) have any uses. The Pentium Pro performs poorly with 16-bit code which makes running Windows 3.1 or 95 on it undesirable

Early Linux may also be an option for this device as emulation via 86box is ''difficult''


Images of this device also show several (unknown) expansion cards from what ever it was being used for originally. These have been removed after photographing

[[File:PXL 20250214 033500161.jpg|thumb|alt=XPS Pro 200N (front)|XPS Pro 200N (front)]]
[[File:PXL 20250214 033516741.jpg|thumb|alt=XPS Pro 200N (rear)|PS Pro 200N (rear)]]</text>
    <sha1>4f105ea80b31fed00b7fa53434f59f6b1a4deae7</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>File:Test.jpeg</title>
  <ns>6</ns>
  <id>66</id>
  <revision>
    <id>107</id>
    <timestamp>2025-02-14T23:28:18Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>File:Optiplex GX1 (Front).jpg</title>
  <ns>6</ns>
  <id>67</id>
  <revision>
    <id>109</id>
    <timestamp>2025-02-17T18:46:46Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20" xml:space="preserve">Optiplex GX1 (Front)</text>
    <sha1>d0f221921efa1a65985493149d704d62d3b4f507</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>File:Optiplex GX1 (Rear).jpg</title>
  <ns>6</ns>
  <id>68</id>
  <revision>
    <id>110</id>
    <timestamp>2025-02-17T18:47:07Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19" xml:space="preserve">Optiplex GX1 (Rear)</text>
    <sha1>cd4be2230e467dfae172379dc59947609f745116</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>File:XPS D266 (front).jpg</title>
  <ns>6</ns>
  <id>70</id>
  <revision>
    <id>112</id>
    <timestamp>2025-02-17T18:52:13Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16" xml:space="preserve">XPS D266 (front)</text>
    <sha1>fcb17e3331e0c6ac7f817f334792a08f848428b4</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>File:XPS D266 (rear).jpg</title>
  <ns>6</ns>
  <id>71</id>
  <revision>
    <id>113</id>
    <timestamp>2025-02-17T18:53:12Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15" xml:space="preserve">XPS D266 (rear)</text>
    <sha1>2add2a9e4494a8f30c78ffd0445408295d8b13ad</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>Dimension XPS D266</title>
  <ns>0</ns>
  <id>72</id>
  <revision>
    <id>114</id>
    <timestamp>2025-02-17T18:53:20Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "As with the other Dell towers, this unit was another pickup from the University of Washington auction  Also similarly to the newer [[Optiplex GX1]] this nit also includes a proprietary power supply.  According to TheRetroWeb this unit could be outfitted with a 233/266/300/333Mhz Pentium II, making this 266 a "mid-range" model. RAM could be expanded up to 3x 128MB of SDR UDIMM's (384MB total)  This unit also appears to contain a (likely IDE based) ZIP 250MB drive. Though..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="649" xml:space="preserve">As with the other Dell towers, this unit was another pickup from the University of Washington auction

Also similarly to the newer [[Optiplex GX1]] this nit also includes a proprietary power supply.

According to TheRetroWeb this unit could be outfitted with a 233/266/300/333Mhz Pentium II, making this 266 a "mid-range" model. RAM could be expanded up to 3x 128MB of SDR UDIMM's (384MB total)

This unit also appears to contain a (likely IDE based) ZIP 250MB drive. Though it is untested at this time.

[[File:XPS D266 (front).jpg|thumb|alt=XPS D266 (front)|XPS D266 (front)]]
[[File:XPS D266 (rear).jpg|thumb|alt=XPS D266 (rear)|XPS D266 (rear)]]</text>
    <sha1>75594e2871d12df7159ca6ae756ca837fff14caf</sha1>
  </revision>
  <revision>
    <id>115</id>
    <parentid>114</parentid>
    <timestamp>2025-02-17T18:53:46Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="662" xml:space="preserve">As with the other Dell towers, this unit was another pickup from the University of Washington auction

Also similarly to the newer [[OptiPlex GX1|Optiplex GX1]] this nit also includes a proprietary power supply.

According to TheRetroWeb this unit could be outfitted with a 233/266/300/333Mhz Pentium II, making this 266 a "mid-range" model. RAM could be expanded up to 3x 128MB of SDR UDIMM's (384MB total)

This unit also appears to contain a (likely IDE based) ZIP 250MB drive. Though it is untested at this time.

[[File:XPS D266 (front).jpg|thumb|alt=XPS D266 (front)|XPS D266 (front)]]
[[File:XPS D266 (rear).jpg|thumb|alt=XPS D266 (rear)|XPS D266 (rear)]]</text>
    <sha1>8f6dc7cb60fbfe7563a00a94fe604ab59871a254</sha1>
  </revision>
  <revision>
    <id>116</id>
    <parentid>115</parentid>
    <timestamp>2025-02-17T18:53:55Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="663" xml:space="preserve">As with the other Dell towers, this unit was another pickup from the University of Washington auction

Also similarly to the newer [[OptiPlex GX1|Optiplex GX1]] this unit also includes a proprietary power supply.

According to TheRetroWeb this unit could be outfitted with a 233/266/300/333Mhz Pentium II, making this 266 a "mid-range" model. RAM could be expanded up to 3x 128MB of SDR UDIMM's (384MB total)

This unit also appears to contain a (likely IDE based) ZIP 250MB drive. Though it is untested at this time.

[[File:XPS D266 (front).jpg|thumb|alt=XPS D266 (front)|XPS D266 (front)]]
[[File:XPS D266 (rear).jpg|thumb|alt=XPS D266 (rear)|XPS D266 (rear)]]</text>
    <sha1>b5e597822dcbb95ef28833b20c6c3d32f64e5dc8</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>Old Computers</title>
  <ns>0</ns>
  <id>2</id>
  <revision>
    <id>117</id>
    <parentid>81</parentid>
    <timestamp>2025-02-18T00:10:17Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1246" xml:space="preserve">As the title suggests, and indeed why you're here. '''''I have a lot of old computers'''''

This page serves as an index catalog of them for easy reference.

&lt;big&gt;'''NOTE: This list is non-exhaustive as I'm constantly picking up new weird old tech'''&lt;/big&gt;


=== Acer Inc ===
[[Acer EasyStore H340]]

=== Apple Computers Inc ===
[[Powermac G4]] "Mirror Drive Door" (MDD)

[[Powermac G5]] Quad

[[eMac G4]]

[[Xserve G4]]

[[Xserve G5]]
=== Cobalt Networks ===
[[Cobalt Qube]]

[[Cobalt RaQ|Cobalt RaQ4]]

=== Dell Computers ===
[[PowerEdge 2500]]

[[OptiPlex GX1]]

[[Dell XPS Pro200N|XPS Pro200N]]

[[Dimension XPS D266]]

=== Digital Equipment Corporation ===
[[DEC AlphaServer 2100|DEC AlphaServer 2100 4/275]]

=== Hewlett Packard ===
[[HP MediaSmart EX495]]

[[HP KAYAK XA 6/400 MT]]

=== Silicon Graphics ===
[[SGI Octane]]

[[SGI Visual Workstation 320]]

=== Sun Microsystems ===
[[Netra X1]]

[[Netra T1]]

[[SunFire Enterprise 420R]] 

[[Ultra 10 Workstation]]

=== Whitebox/custom builds ===

[[Windows 98 PC|World's Fastest Windows 98 PC]]

[[Disc Ripper|Disc Ripper aka "Napster"]]

=== Miscellaneous (Anything not 'retro') ===
[[Framework 13]]

[[Main Desktop]]

[[Home Server]]

[[Hyve Zeus]]

[[Hyve Cygnus]]

[[Video Capture PC]]</text>
    <sha1>0f1c47e7555c0e41e1bc029afd0e52aa96c25748</sha1>
  </revision>
  <revision>
    <id>142</id>
    <parentid>117</parentid>
    <timestamp>2025-04-18T23:21:11Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Mac Mini G4 added</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1263" xml:space="preserve">As the title suggests, and indeed why you're here. '''''I have a lot of old computers'''''

This page serves as an index catalog of them for easy reference.

&lt;big&gt;'''NOTE: This list is non-exhaustive as I'm constantly picking up new weird old tech'''&lt;/big&gt;


=== Acer Inc ===
[[Acer EasyStore H340]]

=== Apple Computers Inc ===
[[Powermac G4]] "Mirror Drive Door" (MDD)

[[Powermac G5]] Quad

[[eMac G4]]

[[Mac Mini G4]]

[[Xserve G4]]

[[Xserve G5]]
=== Cobalt Networks ===
[[Cobalt Qube]]

[[Cobalt RaQ|Cobalt RaQ4]]

=== Dell Computers ===
[[PowerEdge 2500]]

[[OptiPlex GX1]]

[[Dell XPS Pro200N|XPS Pro200N]]

[[Dimension XPS D266]]

=== Digital Equipment Corporation ===
[[DEC AlphaServer 2100|DEC AlphaServer 2100 4/275]]

=== Hewlett Packard ===
[[HP MediaSmart EX495]]

[[HP KAYAK XA 6/400 MT]]

=== Silicon Graphics ===
[[SGI Octane]]

[[SGI Visual Workstation 320]]

=== Sun Microsystems ===
[[Netra X1]]

[[Netra T1]]

[[SunFire Enterprise 420R]] 

[[Ultra 10 Workstation]]

=== Whitebox/custom builds ===

[[Windows 98 PC|World's Fastest Windows 98 PC]]

[[Disc Ripper|Disc Ripper aka "Napster"]]

=== Miscellaneous (Anything not 'retro') ===
[[Framework 13]]

[[Main Desktop]]

[[Home Server]]

[[Hyve Zeus]]

[[Hyve Cygnus]]

[[Video Capture PC]]</text>
    <sha1>8684a842fa7066e7d07db49ecc6e84fb6ba1a21d</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>IMac G3 "Blueberry"</title>
  <ns>0</ns>
  <id>73</id>
  <revision>
    <id>119</id>
    <timestamp>2025-02-18T00:17:08Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "TBA"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3" xml:space="preserve">TBA</text>
    <sha1>ae50ce81c0ab15346851715818b855eed68b0618</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>User:CursedSilicon</title>
  <ns>2</ns>
  <id>74</id>
  <revision>
    <id>120</id>
    <timestamp>2025-02-20T01:30:43Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Oh. Apparently I have a page for myself as a user  If you need me for anything please reach out to my Mastodon  https://social.restless.systems/@CursedSilicon"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="158" xml:space="preserve">Oh. Apparently I have a page for myself as a user

If you need me for anything please reach out to my Mastodon

https://social.restless.systems/@CursedSilicon</text>
    <sha1>218cca8b4b8240ff36298a12b4f13300c16ea631</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>Compu-Global-Hyper-Mega-Net</title>
  <ns>0</ns>
  <id>61</id>
  <revision>
    <id>121</id>
    <parentid>101</parentid>
    <timestamp>2025-02-20T19:51:27Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>The question mark gets stripped from embedding the URL which breaks hotlinking to the specific point in the page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5855" xml:space="preserve">=== Preamble ===
Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in its embryonic stages as I step through the trial-by-fire of the reality of setting up 1990's era telecommunications infrastructure in a way that is both functional and not inconvenient for myself or others in the space it is physically housed in.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "fun" for us!


A longer term goal includes providing democratized access for users to begin submitting their own projects and content ala [[wikipedia:GeoCities|Geocities]] and setting up federated networking with other retro computing users, similar to GlobalTalk but with a larger scope of features and functionality
=== So what's this all about? ===


CGHMN is a collaborative project aimed to create a late 1990's/early 2000's compatible "internet" for retro computing enthusiasts and their machines

=== Okay so how do I connect to it ===


We're currently exploring the best way(s) to allow users to connect their machines to the network. Our intention is to provide as varied a list of options as possible. Current outlined methods under investigation are

* '''Real V.92 Dial-Up service'''. Pending the ability to acquire a [[wikipedia:Primary_Rate_Interface|PRI line]] we would be able to provide dial-in services via a 425 or 206 area code phone number. This service would likely be limited to 24 concurrent users and would be shared with VoIP users
* '''Dial-In via VoIP'''. A user on Mastodon has claimed to have successfully run Dial-Up service over VoIP even with an international connection from China to South America. This needs to be explored further
* '''Ethernet tunneling/emulation'''. Similar to how early DOCSIS Cable modems worked with just an ethernet jack on the rear of the device and DHCP. Users can purchase an '''''OpenWRT compatible''''' device such as a Raspberry Pi (any model) or a [https://store-us.gl-inet.com/products/us-local-delivery-shadow-mini-smart-router-powerful-wireless-performance-travel-wifi-gl-ar300m16 GL-AR300M16] and then connect to the network. A network switch can be optionally used to connect multiple devices in parallel, or a router may be preferable in order to add NAT functionality and prevent local network services (such as DHCP) from "leaking" back out into the wider network.

=== How fast is it? ===


Total internal network capacity is '''''1Gbps''''' (symmetric) due to limitations of the switches in operation. This speed may be raised or lowered depending on future federation with other members. 

Current plans are to offer V.92 (56Kbps), DSL (1Mbps/256K) and T1 (1.5Mbps symmetric) services.

An optional donation tier may be added (either 10Mbps or 100Mbps) for users who want to financially support the network (costs of electricity, server upkeep and other factors)

=== Is this safe to use? I thought connecting old PC's to the internet was a bad idea! ===


Compu-Global-Hyper-Mega-Net is not accessible by the wider internet and is specifically designed to be a ''hermetically sealed'' network. Users can only connect via the above methods '''and can only communicate with other devices on the network'''. Users that violate the Terms of Service or attempt to abuse the network (or other members) will have their access '''permanently removed'''. With that said the usual rules about not downloading suspicious files and other "internet hygiene" rules still apply. While we don't expect bad actors to be a problem, please ensure that any files contributed to the network are scanned for malware first! [https://www.virustotal.com/gui/home/upload VirusTotal] provides free scanning services for this.

=== How can I help? ===


A lot of folks have offered to donate server hosting which is wonderful. Though not (yet!) required. The two biggest things we need are 


'''Donations to buy infrastructure''' (Particularly hard disks!) there's an Amazon Wishlist here that will get updated over time. https://www.amazon.com/hz/wishlist/ls/1W3S0E9IN7ZB7?ref_=wl_share


'''Volunteers who want to set up services'''. Once we've got the servers set up and running, well, we need '''''stuff''''' to run on them. Wanna make a 90's website or run a server for some old game you like? Get in touch [https://social.restless.systems/@CursedSilicon via Mastodon], [https://discord.gg/scMGtSnx5c or via the Discord server]</text>
    <sha1>0c3edf13809364142f20017fedfe087b7041e80a</sha1>
  </revision>
  <revision>
    <id>137</id>
    <parentid>121</parentid>
    <timestamp>2025-04-03T21:06:43Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Tweaking as the service has evolved</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4101" xml:space="preserve">=== Preamble ===
Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in its embryonic stages as I step through the trial-by-fire of the reality of setting up 1990's era telecommunications infrastructure in a way that is both functional and not inconvenient for myself or others in the space it is physically housed in.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "fun" for us!


A longer term goal includes providing democratized access for users to begin submitting their own projects and content ala [[wikipedia:GeoCities|Geocities]] and setting up federated networking with other retro computing users, similar to GlobalTalk but with a larger scope of features and functionality
=== So what's this all about? ===


CGHMN is a collaborative project aimed to create a late 1990's/early 2000's compatible "internet" for retro computing enthusiasts and their machines

=== Okay so how do I connect to it ===


You can sign up '''[[Signup|right now]]!''' to "alpha test" the network

===  How fast is it? ===


Total internal network capacity is '''''1Gbps''''' (symmetric) due to limitations of the switches in operation. This speed may be raised or lowered depending on future federation with other members. 

=== Is this safe to use? I thought connecting old PC's to the internet was a bad idea! ===


Compu-Global-Hyper-Mega-Net is not accessible by the wider internet and is specifically designed to be a ''hermetically sealed'' network. Users can only connect via the above methods '''and can only communicate with other devices on the network'''. Users that violate the Terms of Service or attempt to abuse the network (or other members) will have their access '''permanently removed'''. With that said the usual rules about not downloading suspicious files and other "internet hygiene" rules still apply. While we don't expect bad actors to be a problem, please ensure that any files contributed to the network are scanned for malware first! [https://www.virustotal.com/gui/home/upload VirusTotal] provides free scanning services for this.

=== How can I help? ===


A lot of folks have offered to donate server hosting which is wonderful. Though not (yet!) required. The two biggest things we need are 


'''Donations to buy infrastructure''' (Particularly hard disks!) there's an Amazon Wishlist here that will get updated over time. https://www.amazon.com/hz/wishlist/ls/1W3S0E9IN7ZB7?ref_=wl_share


'''Volunteers who want to set up services'''. Want to come build a website? Run an old game server? Have some weird retro hardware you want to attach to the network? Please, reach out!</text>
    <sha1>64d9654a94aa10ebd6b008ed8873782fd0cb83e1</sha1>
  </revision>
  <revision>
    <id>138</id>
    <parentid>137</parentid>
    <timestamp>2025-04-03T21:42:05Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4213" xml:space="preserve">=== Preamble ===
Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in its embryonic stages as I step through the trial-by-fire of the reality of setting up 1990's era telecommunications infrastructure in a way that is both functional and not inconvenient for myself or others in the space it is physically housed in.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "fun" for us!


A longer term goal includes providing democratized access for users to begin submitting their own projects and content ala [[wikipedia:GeoCities|Geocities]] and setting up federated networking with other retro computing users, similar to GlobalTalk but with a larger scope of features and functionality
=== So what's this all about? ===


CGHMN is a collaborative project aimed to create a late 1990's/early 2000's compatible "internet" for retro computing enthusiasts and their machines

=== Okay so how do I connect to it ===


You can sign up '''[[Signup|right now]]!''' to "alpha test" the network

===  How fast is it? ===


Total internal network capacity is '''''1Gbps''''' (symmetric) due to limitations of the switches in operation. This speed may be raised or lowered depending on future federation with other members. 

Your speed will depend on factors such as how fast your device can run Wireguard and your internet connection 

=== Is this safe to use? I thought connecting old PC's to the internet was a bad idea! ===


Compu-Global-Hyper-Mega-Net is not accessible by the wider internet and is specifically designed to be a ''hermetically sealed'' network. Users can only connect via the above methods '''and can only communicate with other devices on the network'''. Users that violate the Terms of Service or attempt to abuse the network (or other members) will have their access '''permanently removed'''. With that said the usual rules about not downloading suspicious files and other "internet hygiene" rules still apply. While we don't expect bad actors to be a problem, please ensure that any files contributed to the network are scanned for malware first! [https://www.virustotal.com/gui/home/upload VirusTotal] provides free scanning services for this.

=== How can I help? ===


A lot of folks have offered to donate server hosting which is wonderful. Though not (yet!) required. The two biggest things we need are 


'''Donations to buy infrastructure''' (Particularly hard disks!) there's an Amazon Wishlist here that will get updated over time. https://www.amazon.com/hz/wishlist/ls/1W3S0E9IN7ZB7?ref_=wl_share


'''Volunteers who want to set up services'''. Want to come build a website? Run an old game server? Have some weird retro hardware you want to attach to the network? Please, reach out!</text>
    <sha1>4d7cdd6f3a19d054282cae96a34aca394af45542</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>Signup</title>
  <ns>0</ns>
  <id>75</id>
  <revision>
    <id>122</id>
    <timestamp>2025-03-18T18:45:46Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "So! You want to be a member of CompuGlobalHyperMegaNet?  Excellent! Here's how you sign up   Firstly you'll need to join the [https://discord.gg/TnpSG2P677 Cursed Silicon Discord].   Ping one of our Mod staff and request access to the #compu-global-hyper-mega-net channel  Once in there let us know what you'd like to build or run. A few helpful specifics   - Do you have Systems Admin/Network Admin skills? Do you need help with the stuff you'd like to run?  - Are you volun..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="962" xml:space="preserve">So! You want to be a member of CompuGlobalHyperMegaNet?

Excellent! Here's how you sign up


Firstly you'll need to join the [https://discord.gg/TnpSG2P677 Cursed Silicon Discord]. 

Ping one of our Mod staff and request access to the #compu-global-hyper-mega-net channel

Once in there let us know what you'd like to build or run. A few helpful specifics 

- Do you have Systems Admin/Network Admin skills? Do you need help with the stuff you'd like to run?

- Are you volunteering as a single user or are you participating as part of a group?

- Are you intending to use CGHMN's hosting, or do you want to simply attach your own retro hardware to the network?

- What are the best ways we can contact you (usually just in case anything breaks)

Once that's all sorted we'll help you get your project off the ground and running on the network as best we can. 

Once it's up and running though please keep in mind '''you will be responsible for maintaining it'''</text>
    <sha1>39e04dbf52ad0b2e19e743e84b45cb8a20626337</sha1>
  </revision>
  <revision>
    <id>123</id>
    <parentid>122</parentid>
    <timestamp>2025-03-18T18:47:38Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1138" xml:space="preserve">So! You want to be a member of CompuGlobalHyperMegaNet?

Excellent! Here's how you sign up


Firstly you'll need to join the [https://discord.gg/TnpSG2P677 Cursed Silicon Discord].  

Ping one of our Mod staff and request access to the '''#compu-global-hyper-mega-net''' channel


After you've been granted access to the channel, @compu-global-hyper-mega-net and let us know what you'd like to build or run. A few helpful specifics 

* Do you have Systems Admin/Network Admin skills? Do you need help with the stuff you'd like to run?

* Are you volunteering as a single user or are you participating as part of a group?
* Are you intending to use CGHMN's hosting, or do you want to simply attach your own retro hardware to the network?
* What are the best ways we can contact you (usually just in case anything breaks) 

Once that's all sorted we'll help you get your project off the ground and running on the network as best we can. 

Once it's up and running though please keep in mind '''you will be responsible for maintaining it'''
Once it's up and running though please keep in mind '''you will be responsible for maintaining it'''</text>
    <sha1>692bfdc333a2c484c9cf4fe3c492071eeaef5f8a</sha1>
  </revision>
  <revision>
    <id>124</id>
    <parentid>123</parentid>
    <timestamp>2025-03-18T20:39:31Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1037" xml:space="preserve">So! You want to be a member of CompuGlobalHyperMegaNet?

Excellent! Here's how you sign up


Firstly you'll need to join the [https://discord.gg/TnpSG2P677 Cursed Silicon Discord].  

Ping one of our Mod staff and request access to the '''#compu-global-hyper-mega-net''' channel


After you've been granted access to the channel, @compu-global-hyper-mega-net and let us know what you'd like to build or run. A few helpful specifics 

* Do you have Systems Admin/Network Admin skills? Do you need help with the stuff you'd like to run?

* Are you volunteering as a single user or are you participating as part of a group?
* Are you intending to use CGHMN's hosting, or do you want to simply attach your own retro hardware to the network?
* What are the best ways we can contact you (usually just in case anything breaks) 

Once that's all sorted we'll help you get your project off the ground and running on the network as best we can. 

Once it's up and running though please keep in mind '''you will be responsible for maintaining it'''</text>
    <sha1>75c3978ba64709369245ffd122cc5c01a221f437</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>CGHMN-Demo-Network</title>
  <ns>0</ns>
  <id>76</id>
  <revision>
    <id>125</id>
    <timestamp>2025-03-20T02:57:56Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <comment>Details about the demo CGHMN network for the SDF Interim Computer Festival</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13448" xml:space="preserve">=== Demo Network for the Interim Computer Festival ===
This page documents the quickly set up demo network to show off the CGHMN network at the [https://sdf.org/icf/ SDF's Interim Computer Festival] taking place between March 22nd and 23rd. Consider this a sort-of draft, an experimental first version, a test on what might work and what doesn't.

Currently, the basics are up and running on the CGHMN Proxmox hypervisor living in the [https://devhack.net/ /dev/hack Hackerspace] in Seattle. These include a router and Wireguard endpoint through an OPNsense VM, a VXLAN tunnel endpoint container with some custom scripts to make deploying new member tunnel easier and two containers running a basic authoritative BIND DNS server for &lt;code&gt;.cghmn&lt;/code&gt; and &lt;code&gt;.retro&lt;/code&gt; and one hosting a custom, internal Certificate Authority for those domains.

=== Network Layout ===
This section describes the network layout currently set up for the CGHMN demo network, none of which is necessarily permanent and already set in stone. I (Snep) made some assumptions about domain names, IP addresses, firewall rules and general design ideas to get something up and running for the computer festival based on info from the many chats and discussions on the Cursed Silicon Discord's CGHMN channel (See [[Signup]] for more details). So, please feel free to give input on things you'd like to see changed or added!

On the Proxmox host, all VLANs mentioned below are available tagged on the bridge &lt;code&gt;brcghmn&lt;/code&gt;, with exception of VLAN1, which is untagged and the default network when a new container or VM is added to this bridge.

For servers and retro clients, the subnet &lt;code&gt;172.23.0.0/16&lt;/code&gt; is currently in place, divided into smaller subnets, and might be subject to change later down the line. For Wireguard clients, the &lt;code&gt;100.89.128.0/22&lt;/code&gt; subnet out of the CGNAT block is used and again, might change later.

Below is a further breakdown of VLANs existing in this CGHMN demo network:

==== VLAN 1 - The Global LAN (172.23.0.0/22) ====
This network is our layer 2 bridged network to all members who wish to participate and is intended to be used for retro computers to directly communicate with each other even across the globe. This is accomplished by spanning a VXLAN tunnel across a Wireguard connection from the CGHMN server infrastructure to each members' router endpoint, which can be any OpenWRT compatible device that contains the packages for VXLANs and Wireguard. The idea is to bridge on of at least two available interfaces from said router to the VXLAN network and thus directly bridge any connected retro machines to VLAN1. All members will be in the same L2 broadcast domain, meaning even non-IP protocols that are able to run over Ethernet should be able to communicate with each other from all over the world.

Machines on this network are able to connect to all hosts on the Server VLAN (see below), the firewall for DNS, NTP and ICMP queries and to the root DNS and CA servers for DNS queries and HTTP access to the CA web server. They are not, however, able to communicate with any hosts on the internet, the /dev/hack network or any of the other existing VLANs aside from specific exceptions.

Addresses are handed out via DHCP by the router in the range &lt;code&gt;172.23.1.1-172.23.3.254&lt;/code&gt;, the range &lt;code&gt;172.23.1.11-172.23.1.255&lt;/code&gt; is reserved for static hosts. The search domain for this network is &lt;code&gt;clients.retro&lt;/code&gt;.

==== VLAN 4 - Core Services (172.23.4.0/22) ====
This VLAN in intended for core internal services, like the root DNS server, VXLAN endpoint and our custom Certificate Authority. The Proxmox host also has an IP address in this subnet (&lt;code&gt;172.23.4.11&lt;/code&gt;), it does not however have any routes to the rest of this CGHMN demo infrastructure and thus can only be accessed from clients in the Core Services subnet. 

Hosts in this subnet may currently access the internet, the router for DNS, NTP and ICMP queries and the VXLAN endpoint may send UDP datagrams to anyone at port &lt;code&gt;4789&lt;/code&gt; for VXLAN tunnel replies, any other internal connections are prohibited.

Addresses are handed out via DHCP by the router in the range &lt;code&gt;172.23.7.1-172.23.7.254&lt;/code&gt;, the range &lt;code&gt;172.23.4.11-172.23.6.255&lt;/code&gt; is reserved for static hosts. The search domain for this network is &lt;code&gt;core.cghmn&lt;/code&gt;.

==== VLAN 8 - Servers (172.23.8.0/22) ====
This VLAN will contain all servers hosted and managed by members, which can be any (retro) service that works across an IP router. For anything that requires direct layer 2 access or the same broadcast domain as the client machines, it is advised to host said server in the Global LAN network. This is the only VLAN clients from the bridged Global LAN network may access freely, so members should be wary about what ports they open up for anyone outside of localhost. Another option is to run a tiny router instance based on OpenWRT in front of your server which will act as a basic firewall and NAT router behind which one can run their servers.

Hosts in this subnet may not access the internet inherently, however a firewall rule is in place that allows specific servers internet access, it is still uncertain if this will make it to the final CGHMN or if this subnet is also supposed to be entirely sealed off from the public internet. During a few talks on the Discord server, the idea of hosting local package mirrors of popular distros and projects was mentioned so that both modern and retro systems won't need to connect to internet servers for package installations and upgrades. Hosts may access the router for DNS, NTP and ICMP queries, other internal connections are prohibited.

Addresses are handed out via DHCP by the router in the range &lt;code&gt;172.23.11.1-172.23.11.254&lt;/code&gt;, the range &lt;code&gt;172.23.8.11-172.23.10.255&lt;/code&gt; is reserved for static hosts. The search domain for this network is &lt;code&gt;hosting.retro&lt;/code&gt;.

==== VLAN 12 - DMZ (172.23.12.0/22) ====
Currently not in use.

=== Containers and VMs ===
Containers and VMs on the Proxmox host are currently assigned in the 10000 ID range to keep clear of existing VMs.

There is one VM and three containers at the time of writing this:

==== VM 10001 (demo-chhmn-router) ====
This is the OPNsense VM running as the primary router, firewall, DHCP server and Wireguard endpoint for the demo network. Its login credentials are currently in the paws of Snep, as I'm still unsure where any passwords for the CGHMN are going to be stored safely and with proper access rights.

The router has the first IP in any of the available demo network subnets and responds to IPv4 and IPv4 ICMP packets, DNS queries to its local Unbound resolver and NTP sync requests to the built-in NTP server.

Unbound currently resolves all requests it cannot resolve locally recursively against the internet root servers and returns those replies to clients, this may be subject to change as we potentially plan on sealing the network off more. It is configured to forward all requests with a TLD of &lt;code&gt;.cghmn&lt;/code&gt; and &lt;code&gt;.retro&lt;/code&gt; to the internal DNS root server.

The Wireguard endpoint servers as the connection into the CGHMN from the outside internet on &lt;code&gt;66.170.190.194:42070&lt;/code&gt; for anyone that wishes to parttake the network. See [[Signup]] for more details on how to join.

==== Container 10401 (demo-cghmn-root-dns, VLAN4, 172.23.4.101) ====
This container, based on the absolutely tiny-footprinted Alpine image, hosts the BIND-based root DNS server for the internal CGHMN domains &lt;code&gt;.retro&lt;/code&gt; and &lt;code&gt;.cghmn&lt;/code&gt; together with the reverse DNS zone for the 172.23.0.0 network. It lives in the Core Services subnet and is reachable on port 53 for DNS queries from every other internal subnet. Zones are configured in the zone files under &lt;code&gt;/etc/bind/zones&lt;/code&gt; and loaded by the zone blocks in the &lt;code&gt;/etc/named.conf&lt;/code&gt; file.

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10401&lt;/code&gt; on the Proxmox host console.

==== Container 10402 (demo-cghmn-ca, VLAN4, 172.23.4.102) ====
This container, also based on Alpine, is hosting the custom Certificate Authority based on OpenSSL created and self-signed certificate files. It is currently constructed in a Root CA -&gt; Intermediate CA -&gt; Server Certificates structure, where the CA signed certificates of the intermediate CA, which then signs all certificates requested for servers and clients on the network. Clients thus should only need to install the CA certificate into their trusted keychain to have valid TLS connections to servers using certificates signed by this internal CA.

Clients can access a web server on &lt;code&gt;certs.cghmn:80&lt;/code&gt; or &lt;code&gt;172.23.4.102:80&lt;/code&gt; via plain HTTP to download the root CA and intermediate CA certificate files for installation on their retro machines. Note: This is not meant to be secure. When you add this root CA, we could pretend to be any server on the internet under any domain and any system that has the root CA or intermediate CA certificate installed will trust it. Don't add this on machines you would have personal data on or that you would let onto the public internet!

The /root directory of this container contains a script called &lt;code&gt;create-and-sign-server-csr.sh&lt;/code&gt; that, when run without any arguments, will ask a few questions on the command line and generate a signed TLS certificate in the root directory for the specified DNS names to make deployment of new TLS certificates a little easier. This requires the password of the private key of the intermediate CA, which again is currently stored in Sneps password manager but of course will be copied to a safe location to store passwords once available for the CGHMN.

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10401&lt;/code&gt; on the Proxmox host console.

==== Container 10403 (demo-cghmn-vxlan-endpoint, VLAN4, 172.23.4.103) ====
This container, another Alpine instance, connects all the VXLAN clients together under one virtual Linux bridge and is constructed with a couple if-up/if-down scripts and a Bash script to create new tunnels at &lt;code&gt;/opt/vxlan-scripts/create-vxlan-interface.sh&lt;/code&gt;. 

This script, when called like for example so: &lt;code&gt;create-vxlan-interface.sh 100.89.128.90&lt;/code&gt; will do the following:

# Find the first unused VXLAN ID
# Output the VXLAN ID for configuring a new VXLAN tunnel on the client side
# Add an interface configuration to &lt;code&gt;/etc/vxlan-interfaces/&lt;/code&gt; which is sourced by ifupdown
# Bring up that new VXLAN interface, which bridges it to the Global LAN bridge

after which the client with IP 100.89.128.90 can connect a VXLAN tunnel with the newly added VXLAN ID to their router and join the network.

This is still a very manual process, though one which will probably become more streamlined in the future of the CGHMN network, perhaps with some APIs and/or custom OpenWRT web interface *wink wink*.

This container is only reachable by the firewall itself and by the clients connecting their VXLAN bridge to port 4789 from the Wireguard tunnel, as it doesn't do any routing or hosting of services directly aside from the VXLAN endpoint.

=== Proposed Organization of IDs and IPs ===
My (Sneps) idea behind Proxmox container and VM IDs are as follows:

'''101xx - 103xx''' are for Containers and VMs in the bridged layer 2 network, so any hosts that members want to run in the bridged network directly.

'''104xx - 107xx''' are for Containers and VMs in the Core Services VLAN4, so anything that is necessary for the operation of the CGHMN network.

'''108xx - 111xx''' are for Containers and VMs in the Servers VLAN8, so anything that members would choose to host on the CGHMN Proxmox.


For IPs, I left the first 10 IPs in each subnet reserved for things like routers, for example (perhaps a second router and a virtual IP for failover down the line?).

After that, the first half of the subnet (see above under Network Layout for the actual start and end of this range) is supposed to be reserved for any hosts that are set up with a fully static IP. This is entirely outside of the DHCP range to avoid any conflicts. That DHCP range then starts with the second half of the subnet and goes up to the last available host IP of each subnet.

=== Other Notes ===

* Currently, the advertised DNS server via DHCP is the included Unbound Server on the OPNsense instance. If we want to completely seal off clients and servers from the rest of the internet, we could directly point the clients towards our root DNS server for all requests.
* Currently, the OPNsense router does DHCP as it already has an IP in each VLAN and comes with a solid DHCP server that can also support failover out of the box (ISC DHCP). I (Snep) chose this route over a standalone DHCP server to avoid having a second container/VM in each subnet that solely does DHCP or DHCP proxying, mainly to keep the setup and maintenance work as low as possible.
* A customized OpenWRT image for the Gl.iNet MT300n and AR300n are currently being built and tested, which includes required packages and UCI configurations out of the box to make joining the network perhaps a little bit easier. Will update this page or create a new one and link to it once a working image exists!</text>
    <sha1>d7c9d1f31cc5038d6c4b94d0ab2b1c94a415d351</sha1>
  </revision>
  <revision>
    <id>126</id>
    <parentid>125</parentid>
    <timestamp>2025-03-20T03:51:24Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>Added reserved IP for WIREGUARD-EXTERNAL for CursedSilicon</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13541" xml:space="preserve">=== Demo Network for the Interim Computer Festival ===
This page documents the quickly set up demo network to show off the CGHMN network at the [https://sdf.org/icf/ SDF's Interim Computer Festival] taking place between March 22nd and 23rd. Consider this a sort-of draft, an experimental first version, a test on what might work and what doesn't.

Currently, the basics are up and running on the CGHMN Proxmox hypervisor living in the [https://devhack.net/ /dev/hack Hackerspace] in Seattle. These include a router and Wireguard endpoint through an OPNsense VM, a VXLAN tunnel endpoint container with some custom scripts to make deploying new member tunnel easier and two containers running a basic authoritative BIND DNS server for &lt;code&gt;.cghmn&lt;/code&gt; and &lt;code&gt;.retro&lt;/code&gt; and one hosting a custom, internal Certificate Authority for those domains.

=== Network Layout ===
This section describes the network layout currently set up for the CGHMN demo network, none of which is necessarily permanent and already set in stone. I (Snep) made some assumptions about domain names, IP addresses, firewall rules and general design ideas to get something up and running for the computer festival based on info from the many chats and discussions on the Cursed Silicon Discord's CGHMN channel (See [[Signup]] for more details). So, please feel free to give input on things you'd like to see changed or added!

On the Proxmox host, all VLANs mentioned below are available tagged on the bridge &lt;code&gt;brcghmn&lt;/code&gt;, with exception of VLAN1, which is untagged and the default network when a new container or VM is added to this bridge.

For servers and retro clients, the subnet &lt;code&gt;172.23.0.0/16&lt;/code&gt; is currently in place, divided into smaller subnets, and might be subject to change later down the line. For Wireguard clients, the &lt;code&gt;100.89.128.0/22&lt;/code&gt; subnet out of the CGNAT block is used and again, might change later.

Below is a further breakdown of VLANs existing in this CGHMN demo network:

==== VLAN 1 - The Global LAN (172.23.0.0/22) ====
This network is our layer 2 bridged network to all members who wish to participate and is intended to be used for retro computers to directly communicate with each other even across the globe. This is accomplished by spanning a VXLAN tunnel across a Wireguard connection from the CGHMN server infrastructure to each members' router endpoint, which can be any OpenWRT compatible device that contains the packages for VXLANs and Wireguard. The idea is to bridge on of at least two available interfaces from said router to the VXLAN network and thus directly bridge any connected retro machines to VLAN1. All members will be in the same L2 broadcast domain, meaning even non-IP protocols that are able to run over Ethernet should be able to communicate with each other from all over the world.

Machines on this network are able to connect to all hosts on the Server VLAN (see below), the firewall for DNS, NTP and ICMP queries and to the root DNS and CA servers for DNS queries and HTTP access to the CA web server. They are not, however, able to communicate with any hosts on the internet, the /dev/hack network or any of the other existing VLANs aside from specific exceptions.

Addresses are handed out via DHCP by the router in the range &lt;code&gt;172.23.1.1-172.23.3.254&lt;/code&gt;, the range &lt;code&gt;172.23.1.11-172.23.1.255&lt;/code&gt; is reserved for static hosts. The search domain for this network is &lt;code&gt;clients.retro&lt;/code&gt;.

==== VLAN 4 - Core Services (172.23.4.0/22) ====
This VLAN in intended for core internal services, like the root DNS server, VXLAN endpoint and our custom Certificate Authority. The Proxmox host also has an IP address in this subnet (&lt;code&gt;172.23.4.11&lt;/code&gt;), it does not however have any routes to the rest of this CGHMN demo infrastructure and thus can only be accessed from clients in the Core Services subnet. 

Hosts in this subnet may currently access the internet, the router for DNS, NTP and ICMP queries and the VXLAN endpoint may send UDP datagrams to anyone at port &lt;code&gt;4789&lt;/code&gt; for VXLAN tunnel replies, any other internal connections are prohibited.

Addresses are handed out via DHCP by the router in the range &lt;code&gt;172.23.7.1-172.23.7.254&lt;/code&gt;, the range &lt;code&gt;172.23.4.11-172.23.6.255&lt;/code&gt; is reserved for static hosts. The search domain for this network is &lt;code&gt;core.cghmn&lt;/code&gt;.

==== VLAN 8 - Servers (172.23.8.0/22) ====
This VLAN will contain all servers hosted and managed by members, which can be any (retro) service that works across an IP router. For anything that requires direct layer 2 access or the same broadcast domain as the client machines, it is advised to host said server in the Global LAN network. This is the only VLAN clients from the bridged Global LAN network may access freely, so members should be wary about what ports they open up for anyone outside of localhost. Another option is to run a tiny router instance based on OpenWRT in front of your server which will act as a basic firewall and NAT router behind which one can run their servers.

Hosts in this subnet may not access the internet inherently, however a firewall rule is in place that allows specific servers internet access, it is still uncertain if this will make it to the final CGHMN or if this subnet is also supposed to be entirely sealed off from the public internet. During a few talks on the Discord server, the idea of hosting local package mirrors of popular distros and projects was mentioned so that both modern and retro systems won't need to connect to internet servers for package installations and upgrades. Hosts may access the router for DNS, NTP and ICMP queries, other internal connections are prohibited.

Addresses are handed out via DHCP by the router in the range &lt;code&gt;172.23.11.1-172.23.11.254&lt;/code&gt;, the range &lt;code&gt;172.23.8.11-172.23.10.255&lt;/code&gt; is reserved for static hosts. The search domain for this network is &lt;code&gt;hosting.retro&lt;/code&gt;.

==== VLAN 12 - DMZ (172.23.12.0/22) ====
Currently not in use.

=== Containers and VMs ===
Containers and VMs on the Proxmox host are currently assigned in the 10000 ID range to keep clear of existing VMs.

There is one VM and three containers at the time of writing this:

==== VM 10001 (demo-chhmn-router) ====
This is the OPNsense VM running as the primary router, firewall, DHCP server and Wireguard endpoint for the demo network. Its login credentials are currently in the paws of Snep, as I'm still unsure where any passwords for the CGHMN are going to be stored safely and with proper access rights.

The router has the first IP in any of the available demo network subnets and responds to IPv4 and IPv4 ICMP packets, DNS queries to its local Unbound resolver and NTP sync requests to the built-in NTP server.

Unbound currently resolves all requests it cannot resolve locally recursively against the internet root servers and returns those replies to clients, this may be subject to change as we potentially plan on sealing the network off more. It is configured to forward all requests with a TLD of &lt;code&gt;.cghmn&lt;/code&gt; and &lt;code&gt;.retro&lt;/code&gt; to the internal DNS root server.

The Wireguard endpoint servers as the connection into the CGHMN from the outside internet on &lt;code&gt;66.170.190.194:42070&lt;/code&gt; for anyone that wishes to parttake the network. See [[Signup]] for more details on how to join.

==== Container 10401 (demo-cghmn-root-dns, VLAN4, 172.23.4.101) ====
This container, based on the absolutely tiny-footprinted Alpine image, hosts the BIND-based root DNS server for the internal CGHMN domains &lt;code&gt;.retro&lt;/code&gt; and &lt;code&gt;.cghmn&lt;/code&gt; together with the reverse DNS zone for the 172.23.0.0 network. It lives in the Core Services subnet and is reachable on port 53 for DNS queries from every other internal subnet. Zones are configured in the zone files under &lt;code&gt;/etc/bind/zones&lt;/code&gt; and loaded by the zone blocks in the &lt;code&gt;/etc/named.conf&lt;/code&gt; file.

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10401&lt;/code&gt; on the Proxmox host console.

==== Container 10402 (demo-cghmn-ca, VLAN4, 172.23.4.102) ====
This container, also based on Alpine, is hosting the custom Certificate Authority based on OpenSSL created and self-signed certificate files. It is currently constructed in a Root CA -&gt; Intermediate CA -&gt; Server Certificates structure, where the CA signed certificates of the intermediate CA, which then signs all certificates requested for servers and clients on the network. Clients thus should only need to install the CA certificate into their trusted keychain to have valid TLS connections to servers using certificates signed by this internal CA.

Clients can access a web server on &lt;code&gt;certs.cghmn:80&lt;/code&gt; or &lt;code&gt;172.23.4.102:80&lt;/code&gt; via plain HTTP to download the root CA and intermediate CA certificate files for installation on their retro machines. Note: This is not meant to be secure. When you add this root CA, we could pretend to be any server on the internet under any domain and any system that has the root CA or intermediate CA certificate installed will trust it. Don't add this on machines you would have personal data on or that you would let onto the public internet!

The /root directory of this container contains a script called &lt;code&gt;create-and-sign-server-csr.sh&lt;/code&gt; that, when run without any arguments, will ask a few questions on the command line and generate a signed TLS certificate in the root directory for the specified DNS names to make deployment of new TLS certificates a little easier. This requires the password of the private key of the intermediate CA, which again is currently stored in Sneps password manager but of course will be copied to a safe location to store passwords once available for the CGHMN.

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10401&lt;/code&gt; on the Proxmox host console.

==== Container 10403 (demo-cghmn-vxlan-endpoint, VLAN4, 172.23.4.103) ====
This container, another Alpine instance, connects all the VXLAN clients together under one virtual Linux bridge and is constructed with a couple if-up/if-down scripts and a Bash script to create new tunnels at &lt;code&gt;/opt/vxlan-scripts/create-vxlan-interface.sh&lt;/code&gt;. 

This script, when called like for example so: &lt;code&gt;create-vxlan-interface.sh 100.89.128.90&lt;/code&gt; will do the following:

# Find the first unused VXLAN ID
# Output the VXLAN ID for configuring a new VXLAN tunnel on the client side
# Add an interface configuration to &lt;code&gt;/etc/vxlan-interfaces/&lt;/code&gt; which is sourced by ifupdown
# Bring up that new VXLAN interface, which bridges it to the Global LAN bridge

after which the client with IP 100.89.128.90 can connect a VXLAN tunnel with the newly added VXLAN ID to their router and join the network.

This is still a very manual process, though one which will probably become more streamlined in the future of the CGHMN network, perhaps with some APIs and/or custom OpenWRT web interface *wink wink*.

This container is only reachable by the firewall itself and by the clients connecting their VXLAN bridge to port 4789 from the Wireguard tunnel, as it doesn't do any routing or hosting of services directly aside from the VXLAN endpoint.

=== Proposed Organization of IDs and IPs ===
My (Sneps) idea behind Proxmox container and VM IDs are as follows:

'''101xx - 103xx''' are for Containers and VMs in the bridged layer 2 network, so any hosts that members want to run in the bridged network directly.

'''104xx - 107xx''' are for Containers and VMs in the Core Services VLAN4, so anything that is necessary for the operation of the CGHMN network.

'''108xx - 111xx''' are for Containers and VMs in the Servers VLAN8, so anything that members would choose to host on the CGHMN Proxmox.


For IPs, I left the first 10 IPs in each subnet reserved for things like routers, for example (perhaps a second router and a virtual IP for failover down the line?).

After that, the first half of the subnet (see above under Network Layout for the actual start and end of this range) is supposed to be reserved for any hosts that are set up with a fully static IP. This is entirely outside of the DHCP range to avoid any conflicts. That DHCP range then starts with the second half of the subnet and goes up to the last available host IP of each subnet.

=== Other Notes ===

* Currently, the advertised DNS server via DHCP is the included Unbound Server on the OPNsense instance. If we want to completely seal off clients and servers from the rest of the internet, we could directly point the clients towards our root DNS server for all requests.
* Currently, the OPNsense router does DHCP as it already has an IP in each VLAN and comes with a solid DHCP server that can also support failover out of the box (ISC DHCP). I (Snep) chose this route over a standalone DHCP server to avoid having a second container/VM in each subnet that solely does DHCP or DHCP proxying, mainly to keep the setup and maintenance work as low as possible.
* A customized OpenWRT image for the Gl.iNet MT300n and AR300n are currently being built and tested, which includes required packages and UCI configurations out of the box to make joining the network perhaps a little bit easier. Will update this page or create a new one and link to it once a working image exists!

=== Reserved static IPs ===

* '''VLAN1, 172.23.0.11:''' WIREGUARD-EXTERNAL (CursedSilicon)</text>
    <sha1>ff650940efb12e3ffde9f21a8934dd7b61449b47</sha1>
  </revision>
  <revision>
    <id>127</id>
    <parentid>126</parentid>
    <timestamp>2025-03-20T04:49:19Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>added information about the container 10404</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14739" xml:space="preserve">=== Demo Network for the Interim Computer Festival ===
This page documents the quickly set up demo network to show off the CGHMN network at the [https://sdf.org/icf/ SDF's Interim Computer Festival] taking place between March 22nd and 23rd. Consider this a sort-of draft, an experimental first version, a test on what might work and what doesn't.

Currently, the basics are up and running on the CGHMN Proxmox hypervisor living in the [https://devhack.net/ /dev/hack Hackerspace] in Seattle. These include a router and Wireguard endpoint through an OPNsense VM, a VXLAN tunnel endpoint container with some custom scripts to make deploying new member tunnel easier and two containers running a basic authoritative BIND DNS server for &lt;code&gt;.cghmn&lt;/code&gt; and &lt;code&gt;.retro&lt;/code&gt; and one hosting a custom, internal Certificate Authority for those domains.


=== Network Layout ===
This section describes the network layout currently set up for the CGHMN demo network, none of which is necessarily permanent and already set in stone. I (Snep) made some assumptions about domain names, IP addresses, firewall rules and general design ideas to get something up and running for the computer festival based on info from the many chats and discussions on the Cursed Silicon Discord's CGHMN channel (See [[Signup]] for more details). So, please feel free to give input on things you'd like to see changed or added!

On the Proxmox host, all VLANs mentioned below are available tagged on the bridge &lt;code&gt;brcghmn&lt;/code&gt;, with exception of VLAN1, which is untagged and the default network when a new container or VM is added to this bridge.

For servers and retro clients, the subnet &lt;code&gt;172.23.0.0/16&lt;/code&gt; is currently in place, divided into smaller subnets, and might be subject to change later down the line. For Wireguard clients, the &lt;code&gt;100.89.128.0/22&lt;/code&gt; subnet out of the CGNAT block is used and again, might change later.

Below is a further breakdown of VLANs existing in this CGHMN demo network:

==== VLAN 1 - The Global LAN (172.23.0.0/22) ====
This network is our layer 2 bridged network to all members who wish to participate and is intended to be used for retro computers to directly communicate with each other even across the globe. This is accomplished by spanning a VXLAN tunnel across a Wireguard connection from the CGHMN server infrastructure to each members' router endpoint, which can be any OpenWRT compatible device that contains the packages for VXLANs and Wireguard. The idea is to bridge on of at least two available interfaces from said router to the VXLAN network and thus directly bridge any connected retro machines to VLAN1. All members will be in the same L2 broadcast domain, meaning even non-IP protocols that are able to run over Ethernet should be able to communicate with each other from all over the world.

Machines on this network are able to connect to all hosts on the Server VLAN (see below), the firewall for DNS, NTP and ICMP queries and to the root DNS and CA servers for DNS queries and HTTP access to the CA web server. They may also query DNS lookups at the legacy DNS server at &lt;code&gt;172.23.0.104&lt;/code&gt;. They are not, however, able to communicate with any hosts on the internet, the /dev/hack network or any of the other existing VLANs aside from specific exceptions.

Addresses are handed out via DHCP by the router in the range &lt;code&gt;172.23.1.1-172.23.3.254&lt;/code&gt;, the range &lt;code&gt;172.23.1.11-172.23.1.255&lt;/code&gt; is reserved for static hosts. The search domain for this network is &lt;code&gt;clients.retro&lt;/code&gt;.

==== VLAN 4 - Core Services (172.23.4.0/22) ====
This VLAN in intended for core internal services, like the root DNS server, VXLAN endpoint and our custom Certificate Authority. The Proxmox host also has an IP address in this subnet (&lt;code&gt;172.23.4.11&lt;/code&gt;), it does not however have any routes to the rest of this CGHMN demo infrastructure and thus can only be accessed from clients in the Core Services subnet. 

Hosts in this subnet may currently access the internet, the router for DNS, NTP and ICMP queries, query DNS lookups at the legacy DNS server at &lt;code&gt;172.23.4.104&lt;/code&gt; and the VXLAN endpoint may send UDP datagrams to anyone at port &lt;code&gt;4789&lt;/code&gt; for VXLAN tunnel replies, any other internal connections are prohibited.

Addresses are handed out via DHCP by the router in the range &lt;code&gt;172.23.7.1-172.23.7.254&lt;/code&gt;, the range &lt;code&gt;172.23.4.11-172.23.6.255&lt;/code&gt; is reserved for static hosts. The search domain for this network is &lt;code&gt;core.cghmn&lt;/code&gt;.

==== VLAN 8 - Servers (172.23.8.0/22) ====
This VLAN will contain all servers hosted and managed by members, which can be any (retro) service that works across an IP router. For anything that requires direct layer 2 access or the same broadcast domain as the client machines, it is advised to host said server in the Global LAN network. This is the only VLAN clients from the bridged Global LAN network may access freely, so members should be wary about what ports they open up for anyone outside of localhost. Another option is to run a tiny router instance based on OpenWRT in front of your server which will act as a basic firewall and NAT router behind which one can run their servers.

Hosts in this subnet may not access the internet inherently, however a firewall rule is in place that allows specific servers internet access, it is still uncertain if this will make it to the final CGHMN or if this subnet is also supposed to be entirely sealed off from the public internet. During a few chats on the Discord server, the idea of hosting local package mirrors of popular distros and projects was mentioned so that both modern and retro systems won't need to connect to internet servers for package installations and upgrades. Hosts may access the router for DNS, NTP and ICMP queries and query DNS lookups at the legacy DNS server at &lt;code&gt;172.23.4.104&lt;/code&gt;, other internal connections are prohibited.

Addresses are handed out via DHCP by the router in the range &lt;code&gt;172.23.11.1-172.23.11.254&lt;/code&gt;, the range &lt;code&gt;172.23.8.11-172.23.10.255&lt;/code&gt; is reserved for static hosts. The search domain for this network is &lt;code&gt;hosting.retro&lt;/code&gt;.

==== VLAN 12 - DMZ (172.23.12.0/22) ====
Currently not in use.


=== Containers and VMs ===
Containers and VMs on the Proxmox host are currently assigned in the 10000 ID range to keep clear of existing VMs.

There is one VM and three containers at the time of writing this:

==== VM 10001 (demo-chhmn-router) ====
This is the OPNsense VM running as the primary router, firewall, DHCP server and Wireguard endpoint for the demo network. Its login credentials are currently in the paws of Snep, as I'm still unsure where any passwords for the CGHMN are going to be stored safely and with proper access rights.

The router has the first IP in any of the available demo network subnets and responds to IPv4 and IPv4 ICMP packets, DNS queries to its local Unbound resolver and NTP sync requests to the built-in NTP server.

Unbound currently resolves all requests it cannot resolve locally recursively against the internet root servers and returns those replies to clients, this may be subject to change as we potentially plan on sealing the network off more. It is configured to forward all requests with a TLD of &lt;code&gt;.cghmn&lt;/code&gt; and &lt;code&gt;.retro&lt;/code&gt; to the internal DNS root server.

The Wireguard endpoint servers as the connection into the CGHMN from the outside internet on &lt;code&gt;66.170.190.194:42070&lt;/code&gt; for anyone that wishes to parttake the network. See [[Signup]] for more details on how to join.

==== Container 10401 (demo-cghmn-root-dns, VLAN4, 172.23.4.101) ====
This container, based on the absolutely tiny-footprinted Alpine image, hosts the BIND-based root DNS server for the internal CGHMN domains &lt;code&gt;.retro&lt;/code&gt; and &lt;code&gt;.cghmn&lt;/code&gt; together with the reverse DNS zone for the 172.23.0.0 network. It lives in the Core Services subnet and is reachable on port 53 for DNS queries from every other internal subnet. Zones are configured in the zone files under &lt;code&gt;/etc/bind/zones&lt;/code&gt; and loaded by the zone blocks in the &lt;code&gt;/etc/named.conf&lt;/code&gt; file.

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10401&lt;/code&gt; on the Proxmox host console.

==== Container 10402 (demo-cghmn-ca, VLAN4, 172.23.4.102) ====
This container, also based on Alpine, is hosting the custom Certificate Authority based on OpenSSL created and self-signed certificate files. It is currently constructed in a Root CA -&gt; Intermediate CA -&gt; Server Certificates structure, where the CA signed certificates of the intermediate CA, which then signs all certificates requested for servers and clients on the network. Clients thus should only need to install the CA certificate into their trusted keychain to have valid TLS connections to servers using certificates signed by this internal CA.

Clients can access a web server on &lt;code&gt;certs.cghmn:80&lt;/code&gt; or &lt;code&gt;172.23.4.102:80&lt;/code&gt; via plain HTTP to download the root CA and intermediate CA certificate files for installation on their retro machines. Note: This is not meant to be secure. When you add this root CA, we could pretend to be any server on the internet under any domain and any system that has the root CA or intermediate CA certificate installed will trust it. Don't add this on machines you would have personal data on or that you would let onto the public internet!

The /root directory of this container contains a script called &lt;code&gt;create-and-sign-server-csr.sh&lt;/code&gt; that, when run without any arguments, will ask a few questions on the command line and generate a signed TLS certificate in the root directory for the specified DNS names to make deployment of new TLS certificates a little easier. This requires the password of the private key of the intermediate CA, which again is currently stored in Sneps password manager but of course will be copied to a safe location to store passwords once available for the CGHMN.

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10402&lt;/code&gt; on the Proxmox host console.

==== Container 10403 (demo-cghmn-vxlan-endpoint, VLAN4, 172.23.4.103) ====
This container, another Alpine instance, connects all the VXLAN clients together under one virtual Linux bridge and is constructed with a couple if-up/if-down scripts and a Bash script to create new tunnels at &lt;code&gt;/opt/vxlan-scripts/create-vxlan-interface.sh&lt;/code&gt;. 

This script, when called like for example so: &lt;code&gt;create-vxlan-interface.sh 100.89.128.90&lt;/code&gt; will do the following:

# Find the first unused VXLAN ID
# Output the VXLAN ID for configuring a new VXLAN tunnel on the client side
# Add an interface configuration to &lt;code&gt;/etc/vxlan-interfaces/&lt;/code&gt; which is sourced by ifupdown
# Bring up that new VXLAN interface, which bridges it to the Global LAN bridge

after which the client with IP 100.89.128.90 can connect a VXLAN tunnel with the newly added VXLAN ID to their router and join the network.

This is still a very manual process, though one which will probably become more streamlined in the future of the CGHMN network, perhaps with some APIs and/or custom OpenWRT web interface *wink wink*.

This container is only reachable by the firewall itself and by the clients connecting their VXLAN bridge to port 4789 from the Wireguard tunnel, as it doesn't do any routing or hosting of services directly aside from the VXLAN endpoint.

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10403&lt;/code&gt; on the Proxmox host onsole.

==== Container 10404 (demo-cghmn-legacy-dns, VLAN4, 172.23.4.104) ====
This container, based on Alpine, runs a dnsmasq instance configured to look up certain DNS overrides either in the hosts file at &lt;code&gt;/etc/cghmn-dns-overrides&lt;/code&gt; or by including a dnsmasq configuration file from &lt;code&gt;/etc/dnsmasq-cghmn.d/*.conf&lt;/code&gt;. Any other requests it cannot resolve locally are forwarded to the Unbound DNS resolver running on the OPNsense router VM. This setup is used to create DNS overrides for existing domains to make old software, which is hardcoded to specific DNS entries, work again with custom servers hosted internally. 

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10404&lt;/code&gt; on the Proxmox host console.


=== Proposed Organization of IDs and IPs ===
My (Sneps) idea behind Proxmox container and VM IDs are as follows:

'''101xx - 103xx''' are for Containers and VMs in the bridged layer 2 network, so any hosts that members want to run in the bridged network directly.

'''104xx - 107xx''' are for Containers and VMs in the Core Services VLAN4, so anything that is necessary for the operation of the CGHMN network.

'''108xx - 111xx''' are for Containers and VMs in the Servers VLAN8, so anything that members would choose to host on the CGHMN Proxmox.


For IPs, I left the first 10 IPs in each subnet reserved for things like routers, for example (perhaps a second router and a virtual IP for failover down the line?).

After that, the first half of the subnet (see above under Network Layout for the actual start and end of this range) is supposed to be reserved for any hosts that are set up with a fully static IP. This is entirely outside of the DHCP range to avoid any conflicts. That DHCP range then starts with the second half of the subnet and goes up to the last available host IP of each subnet.


=== Other Notes ===

* Currently, the advertised DNS server via DHCP is the included Unbound Server on the OPNsense instance. If we want to completely seal off clients and servers from the rest of the internet, we could directly point the clients towards our root DNS server for all requests.
* Currently, the OPNsense router does DHCP as it already has an IP in each VLAN and comes with a solid DHCP server that can also support failover out of the box (ISC DHCP). I (Snep) chose this route over a standalone DHCP server to avoid having a second container/VM in each subnet that solely does DHCP or DHCP proxying, mainly to keep the setup and maintenance work as low as possible.
* A customized OpenWRT image for the Gl.iNet MT300n and AR300n are currently being built and tested, which includes required packages and UCI configurations out of the box to make joining the network perhaps a little bit easier. Will update this page or create a new one and link to it once a working image exists!


=== Reserved static IPs ===

* '''VLAN1, 172.23.0.11:''' WIREGUARD-EXTERNAL (CursedSilicon)</text>
    <sha1>8e46e1ab3d899eadfec63573601bbda9968d3219</sha1>
  </revision>
  <revision>
    <id>131</id>
    <parentid>127</parentid>
    <timestamp>2025-03-29T20:45:49Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <comment>Added paragraph about changes to the network</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19423" xml:space="preserve">=== Demo Network for the Interim Computer Festival ===
This page documents the quickly set up demo network to show off the CGHMN network at the [https://sdf.org/icf/ SDF's Interim Computer Festival] taking place between March 22nd and 23rd. Consider this a sort-of draft, an experimental first version, a test on what might work and what doesn't.

Currently, the basics are up and running on the CGHMN Proxmox hypervisor living in the [https://devhack.net/ /dev/hack Hackerspace] in Seattle. These include a router and Wireguard endpoint through an OPNsense VM, a VXLAN tunnel endpoint container with some custom scripts to make deploying new member tunnel easier and two containers running a basic authoritative BIND DNS server for &lt;code&gt;.cghmn&lt;/code&gt; and &lt;code&gt;.retro&lt;/code&gt; and one hosting a custom, internal Certificate Authority for those domains.

=== Changes to the network layout ===
Since this page was written, there have been quite a lot of discussions about how and what we might change going forward, after the initial test of the network at the ICF was a success. The biggest change, so far, has been the idea to move away from VXLANs to GRETAP tunnels for the Layer 2 and non-IP Layer 3 traffic. This is mostly due to the fact that VXLANs, by their RFC definition, MAY NOT fragment packets coming into the VTEP (aka. a VXLAN tunnel endpoint) and packets flowing out of a VTEP MAY be reassembled if fragmented, but don't necessarily have to. In addition to this, the IP packets generated by the VXLAN tunnels have the Don't Fragment bit set, so those packets may also not be fragmented. This means that the underlying transport of the VXLAN tunnels, here Wireguard, would have to open a path that allows 1500 byte frames through its tunnel, which would make the tunnel packets themselves quite large at ~1600 bytes, which would then be fragmented by whatever routers are in between the client router and the CGHMN router. Turns out, that's quite inefficient. 

GRETAP tunnels, on the other hand, have the two flags &lt;code&gt;ignore-df&lt;/code&gt; and &lt;code&gt;nopmtudisc&lt;/code&gt;, which together with &lt;code&gt;ttl 255&lt;/code&gt; create a tunnel over IP, which can carry ''and fragment'' 1500 byte Ethernet frames over a smaller underlying transport, still Wireguard in this case. This was a massive boost not only in speed under certain circumstances, like running this all on a small travel router with a weak MIPS CPU, but also reliability, as less dropped packets could be observed and MTU blackholes finally not happening in our testing.

To bring up a GRETAP tunnel within the network to the CGHMN central router, use the following commands on a Linux box:&lt;blockquote&gt;&lt;code&gt;ip link add gretap-cghmn type gretap remote 172.23.4.103 dev wg0 ignore-df nopmtudisc ttl 255&lt;/code&gt;

&lt;code&gt;ip link set gretap-cghmn master br0 mtu 1500&lt;/code&gt;

&lt;code&gt;ip link set gretap-cghmn up&lt;/code&gt;&lt;/blockquote&gt;Where &lt;code&gt;wg0&lt;/code&gt; is your CGHMN Wireguard tunnel and &lt;code&gt;br0&lt;/code&gt; is the bridge you'd want to bridge the GRETAP tunnel to.

However, to improve performance more and make the network a little more reliable, there was another idea for a change: Sending routable IP traffic not over the Layher 2 tunnel, but rather routing it directly through the Wireguard tunnel, which already is a straight Layer 3 path to the CGHMN core router. This is possible due to the nftables &lt;code&gt;bridge&lt;/code&gt; filter table, which can match and filter packets on bridge interfaces, incuding what "bridge port" they come in and go out of. This means we can filter IP traffic from leaving the retro LAN bridge, to which you'd connect your retro machines via a phyiscal LAN port, by creating a filter that says "Block all traffic on bridge &lt;code&gt;br-retrolan&lt;/code&gt; which leaves through a GRETAP interface" and "Block all traffic on bridge &lt;code&gt;br-retrolan&lt;/code&gt; which comes in on a GRETAP interface". Now, you can assign the router a static IP address on the bridge, so it can talk to your retro machines, enable DHCP and NAT and route IP traffic from your machines straight to the CGHMN via Wireguard. In the future, this shall be extended to work without NAT on the client side, so that every member has a small subnet, /24 for example, which is routed to the Wireugard tunnel client IP. This also means that the VLAN1 described in the next section might not need an IP address in the future so that the VLAN1 is purely non-IP traffic at least from the CGHMN side of things.

Yet another idea mentioned was the ability to span tunnels directly between members, even without going through the CGHMN core network in the first place. This can be accomplished by creating another GRETAP interface whose &lt;code&gt;remote&lt;/code&gt; IP argument points to the IP of another members router, either through the existing CGHMN Wireguard tunnel or through a separate tunnel that you span between you and the other member. This GRETAP interface is then bridged to the &lt;code&gt;br-retrolan&lt;/code&gt; bridge and with a couple of (perhaps default) bridge firewall rules, you and the other member should be able to communicate directly! Of course, this also means we'd have to implement some sort of loopback protection not just on the member router side (the default bridge firewall rules mentioned in the last sentence), but also on the core router side. so this idea is not yet fully implemented for testing.

IP Allocations within the network are now kept track of [[CGHMN-IP-Allocations|in this Wiki page]], though the IPs listed there might not be applied in the current configuration yet.


=== Network Layout ===
This section describes the network layout currently set up for the CGHMN demo network, none of which is necessarily permanent and already set in stone. I (Snep) made some assumptions about domain names, IP addresses, firewall rules and general design ideas to get something up and running for the computer festival based on info from the many chats and discussions on the Cursed Silicon Discord's CGHMN channel (See [[Signup]] for more details). So, please feel free to give input on things you'd like to see changed or added!

On the Proxmox host, all VLANs mentioned below are available tagged on the bridge &lt;code&gt;brcghmn&lt;/code&gt;, with exception of VLAN1, which is untagged and the default network when a new container or VM is added to this bridge.

For servers and retro clients, the subnet &lt;code&gt;172.23.0.0/16&lt;/code&gt; is currently in place, divided into smaller subnets, and might be subject to change later down the line. For Wireguard clients, the &lt;code&gt;100.89.128.0/22&lt;/code&gt; subnet out of the CGNAT block is used and again, might change later.

Below is a further breakdown of VLANs existing in this CGHMN demo network:

==== VLAN 1 - The Global LAN (172.23.0.0/22) ====
This network is our layer 2 bridged network to all members who wish to participate and is intended to be used for retro computers to directly communicate with each other even across the globe. This is accomplished by spanning a VXLAN tunnel across a Wireguard connection from the CGHMN server infrastructure to each members' router endpoint, which can be any OpenWRT compatible device that contains the packages for VXLANs and Wireguard. The idea is to bridge on of at least two available interfaces from said router to the VXLAN network and thus directly bridge any connected retro machines to VLAN1. All members will be in the same L2 broadcast domain, meaning even non-IP protocols that are able to run over Ethernet should be able to communicate with each other from all over the world.

Machines on this network are able to connect to all hosts on the Server VLAN (see below), the firewall for DNS, NTP and ICMP queries and to the root DNS and CA servers for DNS queries and HTTP access to the CA web server. They may also query DNS lookups at the legacy DNS server at &lt;code&gt;172.23.0.104&lt;/code&gt;. They are not, however, able to communicate with any hosts on the internet, the /dev/hack network or any of the other existing VLANs aside from specific exceptions.

Addresses are handed out via DHCP by the router in the range &lt;code&gt;172.23.1.1-172.23.3.254&lt;/code&gt;, the range &lt;code&gt;172.23.1.11-172.23.1.255&lt;/code&gt; is reserved for static hosts. The search domain for this network is &lt;code&gt;clients.retro&lt;/code&gt;.

==== VLAN 4 - Core Services (172.23.4.0/22) ====
This VLAN in intended for core internal services, like the root DNS server, VXLAN endpoint and our custom Certificate Authority. The Proxmox host also has an IP address in this subnet (&lt;code&gt;172.23.4.11&lt;/code&gt;), it does not however have any routes to the rest of this CGHMN demo infrastructure and thus can only be accessed from clients in the Core Services subnet. 

Hosts in this subnet may currently access the internet, the router for DNS, NTP and ICMP queries, query DNS lookups at the legacy DNS server at &lt;code&gt;172.23.4.104&lt;/code&gt; and the VXLAN endpoint may send UDP datagrams to anyone at port &lt;code&gt;4789&lt;/code&gt; for VXLAN tunnel replies, any other internal connections are prohibited.

Addresses are handed out via DHCP by the router in the range &lt;code&gt;172.23.7.1-172.23.7.254&lt;/code&gt;, the range &lt;code&gt;172.23.4.11-172.23.6.255&lt;/code&gt; is reserved for static hosts. The search domain for this network is &lt;code&gt;core.cghmn&lt;/code&gt;.

==== VLAN 8 - Servers (172.23.8.0/22) ====
This VLAN will contain all servers hosted and managed by members, which can be any (retro) service that works across an IP router. For anything that requires direct layer 2 access or the same broadcast domain as the client machines, it is advised to host said server in the Global LAN network. This is the only VLAN clients from the bridged Global LAN network may access freely, so members should be wary about what ports they open up for anyone outside of localhost. Another option is to run a tiny router instance based on OpenWRT in front of your server which will act as a basic firewall and NAT router behind which one can run their servers.

Hosts in this subnet may not access the internet inherently, however a firewall rule is in place that allows specific servers internet access, it is still uncertain if this will make it to the final CGHMN or if this subnet is also supposed to be entirely sealed off from the public internet. During a few chats on the Discord server, the idea of hosting local package mirrors of popular distros and projects was mentioned so that both modern and retro systems won't need to connect to internet servers for package installations and upgrades. Hosts may access the router for DNS, NTP and ICMP queries and query DNS lookups at the legacy DNS server at &lt;code&gt;172.23.4.104&lt;/code&gt;, other internal connections are prohibited.

Addresses are handed out via DHCP by the router in the range &lt;code&gt;172.23.11.1-172.23.11.254&lt;/code&gt;, the range &lt;code&gt;172.23.8.11-172.23.10.255&lt;/code&gt; is reserved for static hosts. The search domain for this network is &lt;code&gt;hosting.retro&lt;/code&gt;.

==== VLAN 12 - DMZ (172.23.12.0/22) ====
Currently not in use.


=== Containers and VMs ===
Containers and VMs on the Proxmox host are currently assigned in the 10000 ID range to keep clear of existing VMs.

There is one VM and three containers at the time of writing this:

==== VM 10001 (demo-chhmn-router) ====
This is the OPNsense VM running as the primary router, firewall, DHCP server and Wireguard endpoint for the demo network. Its login credentials are currently in the paws of Snep, as I'm still unsure where any passwords for the CGHMN are going to be stored safely and with proper access rights.

The router has the first IP in any of the available demo network subnets and responds to IPv4 and IPv4 ICMP packets, DNS queries to its local Unbound resolver and NTP sync requests to the built-in NTP server.

Unbound currently resolves all requests it cannot resolve locally recursively against the internet root servers and returns those replies to clients, this may be subject to change as we potentially plan on sealing the network off more. It is configured to forward all requests with a TLD of &lt;code&gt;.cghmn&lt;/code&gt; and &lt;code&gt;.retro&lt;/code&gt; to the internal DNS root server.

The Wireguard endpoint servers as the connection into the CGHMN from the outside internet on &lt;code&gt;66.170.190.194:42070&lt;/code&gt; for anyone that wishes to parttake the network. See [[Signup]] for more details on how to join.

==== Container 10401 (demo-cghmn-root-dns, VLAN4, 172.23.4.101) ====
This container, based on the absolutely tiny-footprinted Alpine image, hosts the BIND-based root DNS server for the internal CGHMN domains &lt;code&gt;.retro&lt;/code&gt; and &lt;code&gt;.cghmn&lt;/code&gt; together with the reverse DNS zone for the 172.23.0.0 network. It lives in the Core Services subnet and is reachable on port 53 for DNS queries from every other internal subnet. Zones are configured in the zone files under &lt;code&gt;/etc/bind/zones&lt;/code&gt; and loaded by the zone blocks in the &lt;code&gt;/etc/named.conf&lt;/code&gt; file.

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10401&lt;/code&gt; on the Proxmox host console.

==== Container 10402 (demo-cghmn-ca, VLAN4, 172.23.4.102) ====
This container, also based on Alpine, is hosting the custom Certificate Authority based on OpenSSL created and self-signed certificate files. It is currently constructed in a Root CA -&gt; Intermediate CA -&gt; Server Certificates structure, where the CA signed certificates of the intermediate CA, which then signs all certificates requested for servers and clients on the network. Clients thus should only need to install the CA certificate into their trusted keychain to have valid TLS connections to servers using certificates signed by this internal CA.

Clients can access a web server on &lt;code&gt;certs.cghmn:80&lt;/code&gt; or &lt;code&gt;172.23.4.102:80&lt;/code&gt; via plain HTTP to download the root CA and intermediate CA certificate files for installation on their retro machines. Note: This is not meant to be secure. When you add this root CA, we could pretend to be any server on the internet under any domain and any system that has the root CA or intermediate CA certificate installed will trust it. Don't add this on machines you would have personal data on or that you would let onto the public internet!

The /root directory of this container contains a script called &lt;code&gt;create-and-sign-server-csr.sh&lt;/code&gt; that, when run without any arguments, will ask a few questions on the command line and generate a signed TLS certificate in the root directory for the specified DNS names to make deployment of new TLS certificates a little easier. This requires the password of the private key of the intermediate CA, which again is currently stored in Sneps password manager but of course will be copied to a safe location to store passwords once available for the CGHMN.

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10402&lt;/code&gt; on the Proxmox host console.

==== Container 10403 (demo-cghmn-vxlan-endpoint, VLAN4, 172.23.4.103) ====
This container, another Alpine instance, connects all the VXLAN clients together under one virtual Linux bridge and is constructed with a couple if-up/if-down scripts and a Bash script to create new tunnels at &lt;code&gt;/opt/vxlan-scripts/create-vxlan-interface.sh&lt;/code&gt;. 

This script, when called like for example so: &lt;code&gt;create-vxlan-interface.sh 100.89.128.90&lt;/code&gt; will do the following:

# Find the first unused VXLAN ID
# Output the VXLAN ID for configuring a new VXLAN tunnel on the client side
# Add an interface configuration to &lt;code&gt;/etc/vxlan-interfaces/&lt;/code&gt; which is sourced by ifupdown
# Bring up that new VXLAN interface, which bridges it to the Global LAN bridge

after which the client with IP 100.89.128.90 can connect a VXLAN tunnel with the newly added VXLAN ID to their router and join the network.

This is still a very manual process, though one which will probably become more streamlined in the future of the CGHMN network, perhaps with some APIs and/or custom OpenWRT web interface *wink wink*.

This container is only reachable by the firewall itself and by the clients connecting their VXLAN bridge to port 4789 from the Wireguard tunnel, as it doesn't do any routing or hosting of services directly aside from the VXLAN endpoint.

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10403&lt;/code&gt; on the Proxmox host onsole.

==== Container 10404 (demo-cghmn-legacy-dns, VLAN4, 172.23.4.104) ====
This container, based on Alpine, runs a dnsmasq instance configured to look up certain DNS overrides either in the hosts file at &lt;code&gt;/etc/cghmn-dns-overrides&lt;/code&gt; or by including a dnsmasq configuration file from &lt;code&gt;/etc/dnsmasq-cghmn.d/*.conf&lt;/code&gt;. Any other requests it cannot resolve locally are forwarded to the Unbound DNS resolver running on the OPNsense router VM. This setup is used to create DNS overrides for existing domains to make old software, which is hardcoded to specific DNS entries, work again with custom servers hosted internally. 

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10404&lt;/code&gt; on the Proxmox host console.


=== Proposed Organization of IDs and IPs ===
My (Sneps) idea behind Proxmox container and VM IDs are as follows:

'''101xx - 103xx''' are for Containers and VMs in the bridged layer 2 network, so any hosts that members want to run in the bridged network directly.

'''104xx - 107xx''' are for Containers and VMs in the Core Services VLAN4, so anything that is necessary for the operation of the CGHMN network.

'''108xx - 111xx''' are for Containers and VMs in the Servers VLAN8, so anything that members would choose to host on the CGHMN Proxmox.


For IPs, I left the first 10 IPs in each subnet reserved for things like routers, for example (perhaps a second router and a virtual IP for failover down the line?).

After that, the first half of the subnet (see above under Network Layout for the actual start and end of this range) is supposed to be reserved for any hosts that are set up with a fully static IP. This is entirely outside of the DHCP range to avoid any conflicts. That DHCP range then starts with the second half of the subnet and goes up to the last available host IP of each subnet.


=== Other Notes ===

* Currently, the advertised DNS server via DHCP is the included Unbound Server on the OPNsense instance. If we want to completely seal off clients and servers from the rest of the internet, we could directly point the clients towards our root DNS server for all requests.
* Currently, the OPNsense router does DHCP as it already has an IP in each VLAN and comes with a solid DHCP server that can also support failover out of the box (ISC DHCP). I (Snep) chose this route over a standalone DHCP server to avoid having a second container/VM in each subnet that solely does DHCP or DHCP proxying, mainly to keep the setup and maintenance work as low as possible.
* A customized OpenWRT image for the Gl.iNet MT300n and AR300n are currently being built and tested, which includes required packages and UCI configurations out of the box to make joining the network perhaps a little bit easier. Will update this page or create a new one and link to it once a working image exists!


=== Reserved static IPs ===

* '''VLAN1, 172.23.0.11:''' WIREGUARD-EXTERNAL (CursedSilicon)</text>
    <sha1>1431e634855e74b8418aa58b8a8b30cf471043d0</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>CGHMN-IP-Allocations</title>
  <ns>0</ns>
  <id>77</id>
  <revision>
    <id>128</id>
    <timestamp>2025-03-23T06:23:00Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <comment>Initial page creation</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1148" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Global LAN
|1
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Tunnel IP
!VXLAN ID
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|100.89.128.1
|1001
|100.96.1.0/24
| -
|-
|Talija
|100.89.128.2
|1002
|100.96.2.0/24
| -
|-
|Snep
|100.89.128.3
|1003
|100.96.3.0/24
| -
|}</text>
    <sha1>24cf515e878e030ac4379e05d16039e20ac3abcd</sha1>
  </revision>
  <revision>
    <id>129</id>
    <parentid>128</parentid>
    <timestamp>2025-03-23T06:35:59Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>Changed VLAN1 to VLAN12</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1149" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|12
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Tunnel IP
!VXLAN ID
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|100.89.128.1
|1001
|100.96.1.0/24
| -
|-
|Talija
|100.89.128.2
|1002
|100.96.2.0/24
| -
|-
|Snep
|100.89.128.3
|1003
|100.96.3.0/24
| -
|}</text>
    <sha1>2435f4fa83875ba4f966c726984a26d335316733</sha1>
  </revision>
  <revision>
    <id>130</id>
    <parentid>129</parentid>
    <timestamp>2025-03-23T06:43:21Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>Changed VLAN12 to VLAN256</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1150" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Tunnel IP
!VXLAN ID
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|100.89.128.1
|1001
|100.96.1.0/24
| -
|-
|Talija
|100.89.128.2
|1002
|100.96.2.0/24
| -
|-
|Snep
|100.89.128.3
|1003
|100.96.3.0/24
| -
|}</text>
    <sha1>d35e2b155db1a8a0d3d6f16240ae8a20c0c89077</sha1>
  </revision>
  <revision>
    <id>132</id>
    <parentid>130</parentid>
    <timestamp>2025-03-29T21:13:37Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1168" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|PC tunnel
|100.89.128.3
|100.96.3.0/24
| -
|}</text>
    <sha1>eba9f601b0c2fa4012d22fbe4f603d081f560a21</sha1>
  </revision>
  <revision>
    <id>133</id>
    <parentid>132</parentid>
    <timestamp>2025-03-29T21:15:01Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1218" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|MT300n Router
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|}</text>
    <sha1>4a0dd4545d1f125f92808baecf7fee1a07f619ed</sha1>
  </revision>
  <revision>
    <id>134</id>
    <parentid>133</parentid>
    <timestamp>2025-03-30T05:09:30Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <comment>Added list entries for delegated domains and member servers on the CGHMN Proxmox</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1638" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|MT300n Router
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.100
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|}</text>
    <sha1>6f9cacaf3501f301329383026eb249a55023b4d7</sha1>
  </revision>
  <revision>
    <id>155</id>
    <parentid>134</parentid>
    <timestamp>2025-05-05T22:26:20Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>Added hadn69 and lily</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1732" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|MT300n Router
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| -
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| -
|100.89.128.6
|100.96.6.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.100
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|}</text>
    <sha1>06e8e61b1d3cee0859dd82898310a217934fddc7</sha1>
  </revision>
  <revision>
    <id>157</id>
    <parentid>155</parentid>
    <timestamp>2025-05-06T21:39:25Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>Added theothertom to members list</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1785" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|MT300n Router
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| -
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| -
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| -
|100.89.128.7
|100.96.7.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.100
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|}</text>
    <sha1>8ef76ffd4d4f1e3fcd5c1e3b61a600544e1fcc0f</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>CGHMN-Router-Configuration</title>
  <ns>0</ns>
  <id>78</id>
  <revision>
    <id>135</id>
    <timestamp>2025-04-02T08:24:45Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <comment>Created page with "Example Script to join a Linux box to the network as a router:   &lt;code&gt;#!/bin/bash  # Replace the values below with the ones you got from us when joining # and/or with values that match your setup WG_CONFIG_PATH=/etc/wireguard/wg-cghmn.conf WG_TUNNEL_IP=100.89.128.1 BRIDGED_LAN_INTERFACE=eth1 BRIDGED_LAN_IP=100.96.1.1 BRIDGED_LAN_DHCP_START=100.96.1.100 BRIDGED_LAN_DHCP_END=100.96.1.200  # Bring up Wireguard tunnel ip link add wg-cghmn type wireguard wg setconf wg-cghnm..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2209" xml:space="preserve">Example Script to join a Linux box to the network as a router:


&lt;code&gt;#!/bin/bash

# Replace the values below with the ones you got from us when joining
# and/or with values that match your setup
WG_CONFIG_PATH=/etc/wireguard/wg-cghmn.conf
WG_TUNNEL_IP=100.89.128.1
BRIDGED_LAN_INTERFACE=eth1
BRIDGED_LAN_IP=100.96.1.1
BRIDGED_LAN_DHCP_START=100.96.1.100
BRIDGED_LAN_DHCP_END=100.96.1.200

# Bring up Wireguard tunnel
ip link add wg-cghmn type wireguard
wg setconf wg-cghnm "${WG_CONFIG_PATH}"
ip addr add "${WG_TUNNEL_IP}/22" dev wg-cghmn
ip link set wg-cghmn up

# Add necessary routes to Wireguard interface
ip route add 100.89.128.0/22 dev wg-cghmn
ip route add 172.23.0.0/16 dev wg-cghmn
ip route add 100.96.0.0/13 dev wg-cghmn

# Enable IP forwarding
sysctl -w net.ipv4.ip_forward=1

# Create bridge and add "LAN"-side interface
ip link add br-cghmn type bridge
ip link set br-cghmn up
ip addr flush "${BRIDGED_LAN_INTERFACE}"
ip link set "${BRIDGED_LAN_INTERFACE}" master br-cghmn

# Add "LAN"-side IP address to bridge
ip addr add "${BRIDGED_LAN_IP}/24" dev br-cghmn

# Add nftables rules to prevent IP traffic from leaving the bridge
nft add table bridge filter
nft add chain bridge filter forward '{ type filter hook forward priority 0; }'
nft add rule bridge forward 'oifname gretap* meta ibrname meta nfproto ipv4 br-cghmn drop comment "Drop IPv4 from leaving the bridge"'
nft add rule bridge forward 'iifname gretap* meta ibrname meta nfproto ipv4 br-cghmn drop comment "Drop IPv4 from entering the bridge"'
nft add rule bridge forward 'oifname gretap* meta ibrname meta nfproto ipv6 br-cghmn drop comment "Drop IPv6 from leaving the bridge"'
nft add rule bridge forward 'iifname gretap* meta ibrname meta nfproto ipv6 br-cghmn drop comment "Drop IPv6 from entering the bridge"'

# Create GRETAP interface and add to bridge
ip link add gretap-cghmn type gretap remote 172.23.4.103 ignore-df nopmtudisc ttl 255
ip link set gretap-cghmn master br-cghmn mtu 1500
ip link set br-cghmn mtu 1500
ip link set gretap-cghmn up

# Start dnsmasq as DHCP server
dnsmasq -d -R -P 80 \
    -i "${BRIDGED_LAN_INTERFACE}" \
    -S 100.89.128.0 \
    -F "${BRIDGED_LAN_DHCP_START},${BRIDGED_LAN_DHCP_END}"&lt;/code&gt;</text>
    <sha1>85dc7ebfd01c18a4729ccc497c2e2f120cae1f36</sha1>
  </revision>
  <revision>
    <id>136</id>
    <parentid>135</parentid>
    <timestamp>2025-04-02T08:25:45Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2807" xml:space="preserve">Example Script to join a Linux box to the network as a router:


&lt;code&gt;#!/bin/bash&lt;/code&gt;

&lt;code&gt;# Replace the values below with the ones you got from us when joining&lt;/code&gt;

&lt;code&gt;# and/or with values that match your setup&lt;/code&gt;

&lt;code&gt;WG_CONFIG_PATH=/etc/wireguard/wg-cghmn.conf&lt;/code&gt;

&lt;code&gt;WG_TUNNEL_IP=100.89.128.1&lt;/code&gt;

&lt;code&gt;BRIDGED_LAN_INTERFACE=eth1&lt;/code&gt;

&lt;code&gt;BRIDGED_LAN_IP=100.96.1.1&lt;/code&gt;

&lt;code&gt;BRIDGED_LAN_DHCP_START=100.96.1.100&lt;/code&gt;

&lt;code&gt;BRIDGED_LAN_DHCP_END=100.96.1.200&lt;/code&gt;

&lt;code&gt;# Bring up Wireguard tunnel&lt;/code&gt;

&lt;code&gt;ip link add wg-cghmn type wireguard&lt;/code&gt;

&lt;code&gt;wg setconf wg-cghnm "${WG_CONFIG_PATH}"&lt;/code&gt;

&lt;code&gt;ip addr add "${WG_TUNNEL_IP}/22" dev wg-cghmn&lt;/code&gt;

&lt;code&gt;ip link set wg-cghmn up&lt;/code&gt;

&lt;code&gt;# Add necessary routes to Wireguard interface&lt;/code&gt;

&lt;code&gt;ip route add 100.89.128.0/22 dev wg-cghmn&lt;/code&gt;

&lt;code&gt;ip route add 172.23.0.0/16 dev wg-cghmn&lt;/code&gt;

&lt;code&gt;ip route add 100.96.0.0/13 dev wg-cghmn&lt;/code&gt;

&lt;code&gt;# Enable IP forwarding&lt;/code&gt;

&lt;code&gt;sysctl -w net.ipv4.ip_forward=1&lt;/code&gt;

&lt;code&gt;# Create bridge and add "LAN"-side interface&lt;/code&gt;

&lt;code&gt;ip link add br-cghmn type bridge&lt;/code&gt;

&lt;code&gt;ip link set br-cghmn up&lt;/code&gt;

&lt;code&gt;ip addr flush "${BRIDGED_LAN_INTERFACE}"&lt;/code&gt;

&lt;code&gt;ip link set "${BRIDGED_LAN_INTERFACE}" master br-cghmn&lt;/code&gt;

&lt;code&gt;# Add "LAN"-side IP address to bridge&lt;/code&gt;

&lt;code&gt;ip addr add "${BRIDGED_LAN_IP}/24" dev br-cghmn&lt;/code&gt;

&lt;code&gt;# Add nftables rules to prevent IP traffic from leaving the bridge&lt;/code&gt;

&lt;code&gt;nft add table bridge filter&lt;/code&gt;

&lt;code&gt;nft add chain bridge filter forward '{ type filter hook forward priority 0; }'&lt;/code&gt;

&lt;code&gt;nft add rule bridge forward 'oifname gretap* meta ibrname meta nfproto ipv4 br-cghmn drop comment "Drop IPv4 from leaving the bridge"'&lt;/code&gt;

&lt;code&gt;nft add rule bridge forward 'iifname gretap* meta ibrname meta nfproto ipv4 br-cghmn drop comment "Drop IPv4 from entering the bridge"'&lt;/code&gt;

&lt;code&gt;nft add rule bridge forward 'oifname gretap* meta ibrname meta nfproto ipv6 br-cghmn drop comment "Drop IPv6 from leaving the bridge"'&lt;/code&gt;

&lt;code&gt;nft add rule bridge forward 'iifname gretap* meta ibrname meta nfproto ipv6 br-cghmn drop comment "Drop IPv6 from entering the bridge"'&lt;/code&gt;

&lt;code&gt;# Create GRETAP interface and add to bridge&lt;/code&gt;

&lt;code&gt;ip link add gretap-cghmn type gretap remote 172.23.4.103 ignore-df nopmtudisc ttl 255&lt;/code&gt;

&lt;code&gt;ip link set gretap-cghmn master br-cghmn mtu 1500&lt;/code&gt;

&lt;code&gt;ip link set br-cghmn mtu 1500&lt;/code&gt;

&lt;code&gt;ip link set gretap-cghmn up&lt;/code&gt;

&lt;code&gt;# Start dnsmasq as DHCP server&lt;/code&gt;

&lt;code&gt;dnsmasq -d -R -P 80 \&lt;/code&gt;

&lt;code&gt;   -i "${BRIDGED_LAN_INTERFACE}" \&lt;/code&gt;

&lt;code&gt;   -S 100.89.128.0 \&lt;/code&gt;

&lt;code&gt;   -F "${BRIDGED_LAN_DHCP_START},${BRIDGED_LAN_DHCP_END}"&lt;/code&gt;</text>
    <sha1>51f2f831f140297237f03d417c8ab385a7c0b72b</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>CGHMN 1.0</title>
  <ns>0</ns>
  <id>79</id>
  <revision>
    <id>139</id>
    <timestamp>2025-04-11T00:48:31Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Tracking sheet for "what would we want in a general 1.0 release"   The main blocker currently is access to reliable fiber at /dev/hack. Gaining that should give us ample bandwidth to start allowing broader user access to the network generally  Maybe invite a selection of "retro networking" youtube folks (TheSerialPort, ClabRetro, etc) to help tire kick things? Serena also suggested federation of retro network service providers, so this could be a useful step"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="462" xml:space="preserve">Tracking sheet for "what would we want in a general 1.0 release"


The main blocker currently is access to reliable fiber at /dev/hack. Gaining that should give us ample bandwidth to start allowing broader user access to the network generally

Maybe invite a selection of "retro networking" youtube folks (TheSerialPort, ClabRetro, etc) to help tire kick things? Serena also suggested federation of retro network service providers, so this could be a useful step</text>
    <sha1>745321b2c9ec7bd25b2f1c4136b6ab7bd5457b81</sha1>
  </revision>
  <revision>
    <id>140</id>
    <parentid>139</parentid>
    <timestamp>2025-04-11T00:50:50Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="807" xml:space="preserve">== Tracking sheet for "what would we want in a general 1.0 release" ==


Let's break these down by user just to keep division of labor easy

=== CursedSilicon suggestions ===


The main blocker currently is access to reliable fiber at /dev/hack. Gaining that should give us ample bandwidth to start allowing broader user access to the network generally

Maybe invite a selection of "retro networking" youtube folks (TheSerialPort, ClabRetro, etc) to help tire kick things? Serena also suggested federation of retro network service providers, so this could be a useful step.

NVIDIA GPU in the DL360pG8 (or another Proxmox server) would be helpful. Being able to launch DirectX games in a VM and test them on the network itself. '''Nvidia Quadro is currently on order, testing with "Nvidia GRID" in future'''</text>
    <sha1>0c0e267a52d02e9f59c478cd68645974f238525d</sha1>
  </revision>
  <revision>
    <id>141</id>
    <parentid>140</parentid>
    <timestamp>2025-04-12T00:09:58Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="573" xml:space="preserve">== Tracking sheet for "what would we want in a general 1.0 release" ==


Let's break these down by user just to keep division of labor easy

=== CursedSilicon suggestions ===


The main blocker currently is access to reliable fiber at /dev/hack. Gaining that should give us ample bandwidth to start allowing broader user access to the network generally

Maybe invite a selection of "retro networking" youtube folks (TheSerialPort, ClabRetro, etc) to help tire kick things? Serena also suggested federation of retro network service providers, so this could be a useful step.</text>
    <sha1>f6651692c4621f636d0b7235cc6af337098b4d5a</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>Mac Mini G4</title>
  <ns>0</ns>
  <id>80</id>
  <revision>
    <id>143</id>
    <timestamp>2025-04-18T23:23:13Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "My iMac G3/350 "BlueBerry" died during the March 2025 Interim Computer Festival   So I bought a G4 1.5Ghz Mac Mini from [https://os9.shop some dude in Virginia] who sells refurbed ones running OS 9.2.2 of all things?   It's a maxed out Mac Mini G4 @ 1.5Ghz with 1GB of RAM and a 120GB mSATA SSD on an IDE adapter card   At this time what I'm going to do with it is unclear. I bought it for a data recovery job at work"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="417" xml:space="preserve">My iMac G3/350 "BlueBerry" died during the March 2025 Interim Computer Festival


So I bought a G4 1.5Ghz Mac Mini from [https://os9.shop some dude in Virginia] who sells refurbed ones running OS 9.2.2 of all things?


It's a maxed out Mac Mini G4 @ 1.5Ghz with 1GB of RAM and a 120GB mSATA SSD on an IDE adapter card


At this time what I'm going to do with it is unclear. I bought it for a data recovery job at work</text>
    <sha1>985206391b639dedb3525a402bc8595a71ce30e6</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>Powermac G4</title>
  <ns>0</ns>
  <id>14</id>
  <revision>
    <id>144</id>
    <parentid>38</parentid>
    <timestamp>2025-04-18T23:24:40Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2676" xml:space="preserve">Apple's PowerMac G4 "MDD" or "Mirrored Drive Door" units are common enough and have been documented heavily enough across the internet by people smarter than me that I don't have much to add about them here. 


I currently own two units. A Dual 1.42Ghz "Firewire 800" (FW800) model and a Dual 1.25Ghz FW800 model.

== 1.42Ghz model details ==


This machine is outfitted with the maximum 2GB of memory (1.5GB under MacOS 9.2) and the fastest supported GPU, an Nvidia Ti4600


The 1.42Ghz model is also equipped with a SeriTek/1eVE2+2 expansion card. This card appears(?) to have been discontinued as the SeriTek "Yahoo" store is no longer operational. 


The SeriTek card provides a 64-bit PCI-X (266MB/s) interface for attaching two SATA II hard disks. The PCI-X bandwidth allows attached drives to operate near their theoretical maximum of 300MB/s (SATA II 3Gbps) however in operation due to the old, slow G4 CPU typical data transfer rates are roughly half that. This is still considerably faster than the ATA-66 IDE bus installed on the motherboard as standard.


The SeriTek card also contains an OpenFirmware compatible Boot ROM, allowing the card to be used to boot OS 9 natively. The additional I/O performance massively improves I/O bound workloads such as "StuffIt" and heavier apps such as ClassZilla.


The internals of the 1.42Ghz model have also been modified. The power supply has been replaced with a PicoPSU style unit for ATX PC's (with corresponding adapter cable) along with dual Noctua 40mm fans for additional cooling. The main CPU fan has been replaced with a 120mm Noctua "PPC" Industrial fan. This fan outputs considerably more airflow than the original fan, while maintaining comparable noise levels. The CPU has yet to be measured above 35C while in operation under this configuration.


At this time the machine currently operates with MacOS 9.2 and OS X 10.5.9 "Sorbet Leopard" from a 240GB SSD partitioned 50/50 between the two operating systems


The second port was originally configured with a second 120GB drive for PPC Linux. However the "nouveau" Linux driver causes system lockups due to (known) endianness issues on PowerPC platforms

== 1.25Ghz model details ==


This machine is currently unused. It was purchased for testing upgrading the [[Xserve G4]] with a faster dual processor CPU however this was unsuccessful.  

'''This unit was [https://loganius.org/2025/04/i-bought-a-mac/ later sent to Loganius] and is now their problem''' 
== Images ==
[[File:G4 MDD Front.jpg|none|thumb|G4 MDD front]]
[[File:G4 MDD 1.42Ghz (rear).jpg|none|thumb|G4 MDD 1.42Ghz (rear)]]
[[File:G4 MDD 1.25Ghz (rear).jpg|none|thumb|G4 MDD 1.25Ghz (rear)]]</text>
    <sha1>7b7530c84431c74bb7c5022c4751eab8dcfd55ea</sha1>
  </revision>
  <revision>
    <id>145</id>
    <parentid>144</parentid>
    <timestamp>2025-04-18T23:25:39Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2693" xml:space="preserve">Apple's PowerMac G4 "MDD" or "Mirrored Drive Door" units are common enough and have been documented heavily enough across the internet by people smarter than me that I don't have much to add about them here. 


I currently own &lt;s&gt;two&lt;/s&gt; ONE unit. A Dual 1.42Ghz "Firewire 800" (FW800) model &lt;s&gt;and a Dual 1.25Ghz FW800 model.&lt;/s&gt;

== 1.42Ghz model details ==


This machine is outfitted with the maximum 2GB of memory (1.5GB under MacOS 9.2) and the fastest supported GPU, an Nvidia Ti4600


The 1.42Ghz model is also equipped with a SeriTek/1eVE2+2 expansion card. This card appears(?) to have been discontinued as the SeriTek "Yahoo" store is no longer operational. 


The SeriTek card provides a 64-bit PCI-X (266MB/s) interface for attaching two SATA II hard disks. The PCI-X bandwidth allows attached drives to operate near their theoretical maximum of 300MB/s (SATA II 3Gbps) however in operation due to the old, slow G4 CPU typical data transfer rates are roughly half that. This is still considerably faster than the ATA-66 IDE bus installed on the motherboard as standard.


The SeriTek card also contains an OpenFirmware compatible Boot ROM, allowing the card to be used to boot OS 9 natively. The additional I/O performance massively improves I/O bound workloads such as "StuffIt" and heavier apps such as ClassZilla.


The internals of the 1.42Ghz model have also been modified. The power supply has been replaced with a PicoPSU style unit for ATX PC's (with corresponding adapter cable) along with dual Noctua 40mm fans for additional cooling. The main CPU fan has been replaced with a 120mm Noctua "PPC" Industrial fan. This fan outputs considerably more airflow than the original fan, while maintaining comparable noise levels. The CPU has yet to be measured above 35C while in operation under this configuration.


At this time the machine currently operates with MacOS 9.2 and OS X 10.5.9 "Sorbet Leopard" from a 240GB SSD partitioned 50/50 between the two operating systems


The second port was originally configured with a second 120GB drive for PPC Linux. However the "nouveau" Linux driver causes system lockups due to (known) endianness issues on PowerPC platforms

== 1.25Ghz model details ==


This machine is currently unused. It was purchased for testing upgrading the [[Xserve G4]] with a faster dual processor CPU however this was unsuccessful.  

'''This unit was [https://loganius.org/2025/04/i-bought-a-mac/ later sent to Loganius] and is now their problem''' 
== Images ==
[[File:G4 MDD Front.jpg|none|thumb|G4 MDD front]]
[[File:G4 MDD 1.42Ghz (rear).jpg|none|thumb|G4 MDD 1.42Ghz (rear)]]
[[File:G4 MDD 1.25Ghz (rear).jpg|none|thumb|G4 MDD 1.25Ghz (rear)]]</text>
    <sha1>7425c0c4e9de706d47ce6af08e1d7f42c6366d17</sha1>
  </revision>
  <revision>
    <id>146</id>
    <parentid>145</parentid>
    <timestamp>2025-04-18T23:29:27Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <minor/>
    <comment>The G4 1.25 GHz in question was a FW400 model, not a FW800 model.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2693" xml:space="preserve">Apple's PowerMac G4 "MDD" or "Mirrored Drive Door" units are common enough and have been documented heavily enough across the internet by people smarter than me that I don't have much to add about them here. 


I currently own &lt;s&gt;two&lt;/s&gt; ONE unit. A Dual 1.42Ghz "Firewire 800" (FW800) model &lt;s&gt;and a Dual 1.25Ghz FW400 model.&lt;/s&gt;

== 1.42Ghz model details ==


This machine is outfitted with the maximum 2GB of memory (1.5GB under MacOS 9.2) and the fastest supported GPU, an Nvidia Ti4600


The 1.42Ghz model is also equipped with a SeriTek/1eVE2+2 expansion card. This card appears(?) to have been discontinued as the SeriTek "Yahoo" store is no longer operational. 


The SeriTek card provides a 64-bit PCI-X (266MB/s) interface for attaching two SATA II hard disks. The PCI-X bandwidth allows attached drives to operate near their theoretical maximum of 300MB/s (SATA II 3Gbps) however in operation due to the old, slow G4 CPU typical data transfer rates are roughly half that. This is still considerably faster than the ATA-66 IDE bus installed on the motherboard as standard.


The SeriTek card also contains an OpenFirmware compatible Boot ROM, allowing the card to be used to boot OS 9 natively. The additional I/O performance massively improves I/O bound workloads such as "StuffIt" and heavier apps such as ClassZilla.


The internals of the 1.42Ghz model have also been modified. The power supply has been replaced with a PicoPSU style unit for ATX PC's (with corresponding adapter cable) along with dual Noctua 40mm fans for additional cooling. The main CPU fan has been replaced with a 120mm Noctua "PPC" Industrial fan. This fan outputs considerably more airflow than the original fan, while maintaining comparable noise levels. The CPU has yet to be measured above 35C while in operation under this configuration.


At this time the machine currently operates with MacOS 9.2 and OS X 10.5.9 "Sorbet Leopard" from a 240GB SSD partitioned 50/50 between the two operating systems


The second port was originally configured with a second 120GB drive for PPC Linux. However the "nouveau" Linux driver causes system lockups due to (known) endianness issues on PowerPC platforms

== 1.25Ghz model details ==


This machine is currently unused. It was purchased for testing upgrading the [[Xserve G4]] with a faster dual processor CPU however this was unsuccessful.  

'''This unit was [https://loganius.org/2025/04/i-bought-a-mac/ later sent to Loganius] and is now their problem''' 
== Images ==
[[File:G4 MDD Front.jpg|none|thumb|G4 MDD front]]
[[File:G4 MDD 1.42Ghz (rear).jpg|none|thumb|G4 MDD 1.42Ghz (rear)]]
[[File:G4 MDD 1.25Ghz (rear).jpg|none|thumb|G4 MDD 1.25Ghz (rear)]]</text>
    <sha1>75939edf79f8278414da27ca50208d060d085be6</sha1>
  </revision>
  <revision>
    <id>147</id>
    <parentid>146</parentid>
    <timestamp>2025-04-18T23:36:13Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <minor/>
    <comment>Tweaked some wording.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2679" xml:space="preserve">Apple's PowerMac G4 "MDD" or "Mirrored Drive Door" units are common enough and have been documented heavily enough across the internet by people smarter than me that I don't have much to add about them here. 


I currently own &lt;s&gt;two&lt;/s&gt; ONE unit: a dual 1.42Ghz "FireWire 800" (FW800) model &lt;s&gt;and a dual 1.25Ghz FW400 model.&lt;/s&gt;

== 1.42Ghz model details ==


This machine is outfitted with the maximum 2GB of memory (1.5GB under MacOS 9.2) and the fastest supported GPU, an Nvidia Ti4600


The 1.42Ghz model is also equipped with a SeriTek/1eVE2+2 expansion card. This card appears(?) to have been discontinued as the SeriTek "Yahoo" store is no longer operational. 


The SeriTek card provides a 64-bit PCI-X (266MB/s) interface for attaching two SATA II hard disks. The PCI-X bandwidth allows attached drives to operate near their theoretical maximum of 300MB/s (SATA II 3Gbps) however in operation due to the old, slow G4 CPU typical data transfer rates are roughly half that. This is still considerably faster than the ATA-66 IDE bus installed on the motherboard as standard.


The SeriTek card also contains an OpenFirmware compatible Boot ROM, allowing the card to be used to boot OS 9 natively. The additional I/O performance massively improves I/O bound workloads such as "StuffIt" and heavier apps such as ClassZilla.


The internals of the 1.42Ghz model have also been modified. The power supply has been replaced with a PicoPSU style unit for ATX PC's (with corresponding adapter cable) along with dual Noctua 40mm fans for additional cooling. The main CPU fan has been replaced with a 120mm Noctua "PPC" Industrial fan. This fan outputs considerably more airflow than the original fan, while maintaining comparable noise levels. The CPU has yet to be measured above 35C while in operation under this configuration.


At this time the machine currently operates with MacOS 9.2 and OS X 10.5.9 "Sorbet Leopard" from a 240GB SSD partitioned 50/50 between the two operating systems


The second port was originally configured with a second 120GB drive for PPC Linux. However the "nouveau" Linux driver causes system lockups due to (known) endianness issues on PowerPC platforms

== 1.25Ghz model details ==

This machine was originally purchased for testing upgrading the [[Xserve G4]] with a faster dual processor CPU; however, this was unsuccessful.  

'''It has since been [https://loganius.org/2025/04/i-bought-a-mac/ sent to Loganius] and is now their problem.''' 
== Images ==
[[File:G4 MDD Front.jpg|none|thumb|G4 MDD front]]
[[File:G4 MDD 1.42Ghz (rear).jpg|none|thumb|G4 MDD 1.42Ghz (rear)]]
[[File:G4 MDD 1.25Ghz (rear).jpg|none|thumb|G4 MDD 1.25Ghz (rear)]]</text>
    <sha1>cd593af3b006972b19b732284b5d1c0392ffe80f</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>File:CGHMN.png</title>
  <ns>6</ns>
  <id>81</id>
  <revision>
    <id>148</id>
    <timestamp>2025-04-21T23:47:47Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17" xml:space="preserve">CGHMN demo router</text>
    <sha1>17044fd19548d0e06534146eb2f065b75a58d805</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>How to Get Connected</title>
  <ns>0</ns>
  <id>82</id>
  <revision>
    <id>149</id>
    <timestamp>2025-04-21T23:49:31Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "This is a quick and dirty "how do I get on CGHMN"   Right now since the service is in "closed beta" these steps are a bit vague and manual. But over time as we figure out what works we'll add more connection methods and better documentation  Right now to get connected you effectively need three things:   * '''An ethernet connection on your device of choice. With a TCP/IP (v4) stack! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works'''  * '''Something with the abil..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="935" xml:space="preserve">This is a quick and dirty "how do I get on CGHMN" 

Right now since the service is in "closed beta" these steps are a bit vague and manual. But over time as we figure out what works we'll add more connection methods and better documentation

Right now to get connected you effectively need three things:


* '''An ethernet connection on your device of choice. With a TCP/IP (v4) stack! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works'''

* '''Something with the ability to run Wireguard and gretap. Personally we recommend something running OpenWRT, like a GL-AR300M16. We even have an install script for that which will handle setting it all up for you!
'''
* '''A network switch. Literally any kind of network switch. You plug one end into the Wireguard box and then your clients can all access CGHMN. Super easy'''


If you do everything correctly you'll have a hardware setup something like this


[[File:CGHMN.png|thumb]]</text>
    <sha1>1941bf79ef7b4566b77719f2c5230bd9097db284</sha1>
  </revision>
  <revision>
    <id>151</id>
    <parentid>149</parentid>
    <timestamp>2025-04-24T01:41:57Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <comment>Added OpenWRT tutorial and Admin tutorial</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8035" xml:space="preserve">This is a quick and dirty "how do I get on CGHMN" 

Right now since the service is in "closed beta" these steps are a bit vague and manual. But over time as we figure out what works we'll add more connection methods and better documentation

Right now to get connected you effectively need three things, hardware wise:


[[File:CGHMN.png|thumb|319x319px|Example CGHMN Router Setup using a GL-AR300M and basic network switch]]

=== Hardware requirements ===
To connect your retro machine(s) to the CGHMN, you'll need the following:
*'''An Ethernet connection on your retro device(s) of choice, with a TCP/IP (v4) stack for now! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works.'''

* '''Something with the ability to run Wireguard and forward IPv4 packets at the minimum and, for any non-IP packets, &lt;code&gt;gretap&lt;/code&gt; and &lt;code&gt;nftables&lt;/code&gt;. Personally we recommend something running OpenWRT, like the [https://www.gl-inet.com/products/gl-ar300m GL-AR300M] which we have successfully tested to work. We're currently working on a pre-built image for some select routers to make the setup easier for new members. A script to configure already existing OpenWRT instances can be found below.'''
* Alternatively, you can also run the CGHMN routing on any standard Linux box which has at least one Ethernet port and either a second one or WiFi for internet connectivity. &lt;s&gt;A basic script to set up a Linux machine as a router is posted below&lt;/s&gt; (TODO!).

* '''Optionally: A simple network switch, in case you want to add multiple machines to the network. You plug one end into the CGHMN Router box and then your clients can all access CGHMN. Super easy!'''

On the right is an example of what a CGHMN router setup could look like.

=== Get connected - With OpenWRT ===
If you chose to go with an OpenWRT compatible router or want to run OpenWRT on typical x86 hardware/in a VM, you can follow these steps to get yourself connected to the CGHMN:

# Update your OpenWRT install to the latest version to ensure all required packages are available and compatible.
# Download [https://raw.githubusercontent.com/jonasluehrig/cghmn-get-connected/refs/heads/main/openwrt/setup-cghmn.sh this script from GitHub] to your OpenWRT router via SSH
# Run the following commands on the router:
## &lt;code&gt;ash setup-cghmn.sh install-pkgs&lt;/code&gt;
## &lt;code&gt;ash setup-cghmn.sh init&lt;/code&gt;
## You will be asked what network port you'd like to use for the Retro LAN. This is where you will plug in your retro machines to be part of the CGHMN. Choose a port that is not assigned to any OpenWRT interface like '''lan''' or '''wan''' or which not already part of a bridge and enter the Linux interface name, e.g. &lt;code&gt;eth1&lt;/code&gt;, then press &lt;code&gt;[Enter]&lt;/code&gt; to continue. If your router only has two ports and you're using one for WAN, then you first have to [https://openwrt.org/docs/guide-user/luci/luci.secure#allow_access_from_internet enable the web UI and SSH access via the '''wan''' OpenWRT interface], remove the entire '''lan''' OpenWRT interface to free the network port and continue the setup over the IP address your router got on its WAN side. If you only have a single Ethernet port, you're running on a router setup we can't really recommend, however you can configure VLANs and use a managed switch to both get a WAN DHCP address for internet access and have a separate VLAN for the Retro LAN bridge over a single port. This is commonly referred to as "[[wikipedia:Router_on_a_stick|router on a stick]]". Just enter the VLAN interface name here if you choose to go that route.
# Now you will be given some information on the console, including a Wireguard public key. Send one of the CGHMN admins (currently CursedSilicon and Snep) that key so we can add your router to our Wireguard server.
# In return, you will receive a tunnel IPv4 address (&lt;code&gt;100.89.128.x/32&lt;/code&gt;) and a routed IPv4 subnet (&lt;code&gt;100.96.x.0/24&lt;/code&gt;) from us. These will be needed on the third and final step of the setup script:
## &lt;code&gt;ash setup-cghmn.sh set-tunnel-ip&lt;/code&gt;
# Once the script completed successfully, reboot the router to ensure all interfaces are up properly. After the reboot, your retro devices should receive an IP address in your routed IPv4 subnet on the Retro LAN port you chose above and be able to communicate with other machines on the CGHMN network.


=== Get connected - Server Side, the Admins Guide ===
[[File:Example Configuration for new Wireguard Peer on Core Router.png|thumb|Example Configuration for new Wireguard Peer on Core Router]]
To get a member onto the network, they will send an admin of the project their randomly generated Wireguard key during the setup via the OpenWRT script. Here are the steps that admin will have to follow to get them up and running on the server side:

# Log in on the [https://router.core.cghmn:8443 Core Router] over an existing CGHMN network link
# Navigate to VPN -&gt; Wireguard -&gt; Peer Generator
# You will be asked to enter some data for the new peer, enter the following: '''Instance:''' &lt;code&gt;WG_Member&lt;/code&gt; '''Endpoint:''' &lt;code&gt;wg-admin.cursedsilicon.net:42070&lt;/code&gt;    '''Name:''' &lt;code&gt;member.''&lt;Nickname of the new member&gt;''&lt;/code&gt;    '''Public Key:''' &lt;code&gt;''&lt;their Wireguard public key they've sent over&gt;''&lt;/code&gt;    '''Private Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;    '''Address:''' ''&lt;code&gt;&lt;Next highest IP from 100.89.128.0/22, this is their tunnel IP and is auto-filled&gt;&lt;/code&gt;''    '''Pre-Shared Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;    '''Allowed IPs:''' &lt;code&gt;''&lt;the same as Address&gt;'', ''&lt;their routed subnet, see below&gt;''&lt;/code&gt;    '''Keepalive interval:''' ''&lt;code&gt;&lt;blank&gt;&lt;/code&gt;''    '''DNS Servers:''' &lt;code&gt;''&lt;default value&gt;''&lt;/code&gt;
# Hit the "Store and generate next" button
# Navigate to VPN -&gt; Wireguard -&gt; Instances
# Hit the "Apply" button
# Do either one of these steps, depending on if you can SSH into the GRETAP endpoint container:
## SSH into the CGHMN Proxmox Server and enter the command &lt;code&gt;pct enter 10403&lt;/code&gt;
## SSH directly into the GRETAP endpoint (formerly VXLAN endpoint) container with &lt;code&gt;ssh root@172.23.4.103&lt;/code&gt;
# From there, run the following command: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh &lt;member-tunnel-ip&gt; &lt;member-name&gt;&lt;/code&gt; where you replace &lt;code&gt;&lt;member-tunnel-ip&gt;&lt;/code&gt; with the IP tunnel address of the member as it was set above in the '''Address''' field, without the &lt;code&gt;/32&lt;/code&gt; CIDR subnet mask, and replace the &lt;code&gt;&lt;member-name&gt;&lt;/code&gt; with the same value you've entered above in the '''Name''' field. For example, like this: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh 100.89.128.6 member.snep.test&lt;/code&gt; This will create a GRETAP (and for legacy purposes, a VXLAN) interface and bring them up automagically. ''Ignore the fact it still says "VXLAN" everywhere, it does both.''
# Now you can send the member their Wireguard Tunnel IP and their routed subnet over and they can finish their client-side setup according to the mini-tutorial above.

==== But wait, what even ''is'' their routed subnet? ====
Each members routed subnet comes per default from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IPv4 block and has a &lt;code&gt;/24&lt;/code&gt; mask. This subnet is their "Retro LAN", to which all their retro computers are hooked into via the router of their choosing. By default, NAT is enabled on the routers, so it wouldn't make a difference which subnet is used on the remote end for the retro machines. However, if someone wants to host servers in the CGHMN and doesn't want to do port forwading, they can disable NAT and let other membres directly connect to their machines via this routed subnet.

To get the routed subnet of a member, take the number from the last octet of the Wireguard tunnel IP of a member, say &lt;code&gt;100.89.128.'''6'''&lt;/code&gt;, and put it into the third octet of the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IP block and replace the &lt;code&gt;/13&lt;/code&gt; with &lt;code&gt;/24&lt;/code&gt;, so you get &lt;code&gt;100.96.'''6'''.0/24&lt;/code&gt;. That is their routed subnet, simple as that!</text>
    <sha1>ad35f1cc1970ac18f65d82c8f61e5282a4339b26</sha1>
  </revision>
  <revision>
    <id>152</id>
    <parentid>151</parentid>
    <timestamp>2025-04-24T01:47:15Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>damn linebreaks</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8029" xml:space="preserve">This is a quick and dirty "how do I get on CGHMN" 

Right now since the service is in "closed beta" these steps are a bit vague and manual. But over time as we figure out what works we'll add more connection methods and better documentation

Right now to get connected you effectively need three things, hardware wise:


[[File:CGHMN.png|thumb|319x319px|Example CGHMN Router Setup using a GL-AR300M and basic network switch]]

=== Hardware requirements ===
To connect your retro machine(s) to the CGHMN, you'll need the following:
*'''An Ethernet connection on your retro device(s) of choice, with a TCP/IP (v4) stack for now! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works.'''

* '''Something with the ability to run Wireguard and forward IPv4 packets at the minimum and, for any non-IP packets, &lt;code&gt;gretap&lt;/code&gt; and &lt;code&gt;nftables&lt;/code&gt;. Personally we recommend something running OpenWRT, like the [https://www.gl-inet.com/products/gl-ar300m GL-AR300M] which we have successfully tested to work. We're currently working on a pre-built image for some select routers to make the setup easier for new members. A script to configure already existing OpenWRT instances can be found below.'''
* Alternatively, you can also run the CGHMN routing on any standard Linux box which has at least one Ethernet port and either a second one or WiFi for internet connectivity. &lt;s&gt;A basic script to set up a Linux machine as a router is posted below&lt;/s&gt; (TODO!).

* '''Optionally: A simple network switch, in case you want to add multiple machines to the network. You plug one end into the CGHMN Router box and then your clients can all access CGHMN. Super easy!'''

On the right is an example of what a CGHMN router setup could look like.

=== Get connected - With OpenWRT ===
If you chose to go with an OpenWRT compatible router or want to run OpenWRT on typical x86 hardware/in a VM, you can follow these steps to get yourself connected to the CGHMN:

# Update your OpenWRT install to the latest version to ensure all required packages are available and compatible.
# Download [https://raw.githubusercontent.com/jonasluehrig/cghmn-get-connected/refs/heads/main/openwrt/setup-cghmn.sh this script from GitHub] to your OpenWRT router via SSH
# Run the following commands on the router:
## &lt;code&gt;ash setup-cghmn.sh install-pkgs&lt;/code&gt;
## &lt;code&gt;ash setup-cghmn.sh init&lt;/code&gt;
## You will be asked what network port you'd like to use for the Retro LAN. This is where you will plug in your retro machines to be part of the CGHMN. Choose a port that is not assigned to any OpenWRT interface like '''lan''' or '''wan''' or which not already part of a bridge and enter the Linux interface name, e.g. &lt;code&gt;eth1&lt;/code&gt;, then press &lt;code&gt;[Enter]&lt;/code&gt; to continue. If your router only has two ports and you're using one for WAN, then you first have to [https://openwrt.org/docs/guide-user/luci/luci.secure#allow_access_from_internet enable the web UI and SSH access via the '''wan''' OpenWRT interface], remove the entire '''lan''' OpenWRT interface to free the network port and continue the setup over the IP address your router got on its WAN side. If you only have a single Ethernet port, you're running on a router setup we can't really recommend, however you can configure VLANs and use a managed switch to both get a WAN DHCP address for internet access and have a separate VLAN for the Retro LAN bridge over a single port. This is commonly referred to as "[[wikipedia:Router_on_a_stick|router on a stick]]". Just enter the VLAN interface name here if you choose to go that route.
# Now you will be given some information on the console, including a Wireguard public key. Send one of the CGHMN admins (currently CursedSilicon and Snep) that key so we can add your router to our Wireguard server.
# In return, you will receive a tunnel IPv4 address (&lt;code&gt;100.89.128.x/32&lt;/code&gt;) and a routed IPv4 subnet (&lt;code&gt;100.96.x.0/24&lt;/code&gt;) from us. These will be needed on the third and final step of the setup script:
## &lt;code&gt;ash setup-cghmn.sh set-tunnel-ip&lt;/code&gt;
# Once the script completed successfully, reboot the router to ensure all interfaces are up properly. After the reboot, your retro devices should receive an IP address in your routed IPv4 subnet on the Retro LAN port you chose above and be able to communicate with other machines on the CGHMN network.


=== Get connected - Server Side, the Admins Guide ===
[[File:Example Configuration for new Wireguard Peer on Core Router.png|thumb|Example Configuration for new Wireguard Peer on Core Router]]
To get a member onto the network, they will send an admin of the project their randomly generated Wireguard key during the setup via the OpenWRT script. Here are the steps that admin will have to follow to get them up and running on the server side:

# Log in on the [https://router.core.cghmn:8443 Core Router] over an existing CGHMN network link
# Navigate to VPN -&gt; Wireguard -&gt; Peer Generator
# You will be asked to enter some data for the new peer, enter the following: 
## '''Instance:''' &lt;code&gt;WG_Member&lt;/code&gt;   
## '''Endpoint:''' &lt;code&gt;wg-admin.cursedsilicon.net:42070&lt;/code&gt;
## '''Name:''' &lt;code&gt;member.''&lt;Nickname of the new member&gt;''&lt;/code&gt;
## '''Public Key:''' &lt;code&gt;''&lt;their Wireguard public key they've sent over&gt;''&lt;/code&gt;
## '''Private Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Address:''' ''&lt;code&gt;&lt;Next highest IP from 100.89.128.0/22, this is their tunnel IP and is auto-filled&gt;&lt;/code&gt;''
## '''Pre-Shared Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Allowed IPs:''' &lt;code&gt;''&lt;the same as Address&gt;'', ''&lt;their routed subnet, see below&gt;''&lt;/code&gt;
## '''Keepalive interval:''' ''&lt;code&gt;&lt;blank&gt;&lt;/code&gt;''
## '''DNS Servers:''' &lt;code&gt;''&lt;default value&gt;''&lt;/code&gt;
# Hit the "Store and generate next" button
# Navigate to VPN -&gt; Wireguard -&gt; Instances
# Hit the "Apply" button
# Do either one of these steps, depending on if you can SSH into the GRETAP endpoint container:
## SSH into the CGHMN Proxmox Server and enter the command &lt;code&gt;pct enter 10403&lt;/code&gt;
## SSH directly into the GRETAP endpoint (formerly VXLAN endpoint) container with &lt;code&gt;ssh root@172.23.4.103&lt;/code&gt;
# From there, run the following command: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh &lt;member-tunnel-ip&gt; &lt;member-name&gt;&lt;/code&gt; where you replace &lt;code&gt;&lt;member-tunnel-ip&gt;&lt;/code&gt; with the IP tunnel address of the member as it was set above in the '''Address''' field, without the &lt;code&gt;/32&lt;/code&gt; CIDR subnet mask, and replace the &lt;code&gt;&lt;member-name&gt;&lt;/code&gt; with the same value you've entered above in the '''Name''' field. For example, like this: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh 100.89.128.6 member.snep.test&lt;/code&gt; This will create a GRETAP (and for legacy purposes, a VXLAN) interface and bring them up automagically. ''Ignore the fact it still says "VXLAN" everywhere, it does both.''
# Now you can send the member their Wireguard Tunnel IP and their routed subnet over and they can finish their client-side setup according to the mini-tutorial above.

==== But wait, what even ''is'' their routed subnet? ====
Each members routed subnet comes per default from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IPv4 block and has a &lt;code&gt;/24&lt;/code&gt; mask. This subnet is their "Retro LAN", to which all their retro computers are hooked into via the router of their choosing. By default, NAT is enabled on the routers, so it wouldn't make a difference which subnet is used on the remote end for the retro machines. However, if someone wants to host servers in the CGHMN and doesn't want to do port forwading, they can disable NAT and let other membres directly connect to their machines via this routed subnet.

To get the routed subnet of a member, take the number from the last octet of the Wireguard tunnel IP of a member, say &lt;code&gt;100.89.128.'''6'''&lt;/code&gt;, and put it into the third octet of the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IP block and replace the &lt;code&gt;/13&lt;/code&gt; with &lt;code&gt;/24&lt;/code&gt;, so you get &lt;code&gt;100.96.'''6'''.0/24&lt;/code&gt;. That is their routed subnet, simple as that!</text>
    <sha1>7bc5a1d3c53ab0bc0ba0259592333335b4d7f39d</sha1>
  </revision>
  <revision>
    <id>153</id>
    <parentid>152</parentid>
    <timestamp>2025-04-24T01:48:11Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>Added a link to user admin side tutorial</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8098" xml:space="preserve">This is a quick and dirty "how do I get on CGHMN" 

Right now since the service is in "closed beta" these steps are a bit vague and manual. But over time as we figure out what works we'll add more connection methods and better documentation

Right now to get connected you effectively need three things, hardware wise:


[[File:CGHMN.png|thumb|319x319px|Example CGHMN Router Setup using a GL-AR300M and basic network switch]]

=== Hardware requirements ===
To connect your retro machine(s) to the CGHMN, you'll need the following:
*'''An Ethernet connection on your retro device(s) of choice, with a TCP/IP (v4) stack for now! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works.'''

* '''Something with the ability to run Wireguard and forward IPv4 packets at the minimum and, for any non-IP packets, &lt;code&gt;gretap&lt;/code&gt; and &lt;code&gt;nftables&lt;/code&gt;. Personally we recommend something running OpenWRT, like the [https://www.gl-inet.com/products/gl-ar300m GL-AR300M] which we have successfully tested to work. We're currently working on a pre-built image for some select routers to make the setup easier for new members. A script to configure already existing OpenWRT instances can be found below.'''
* Alternatively, you can also run the CGHMN routing on any standard Linux box which has at least one Ethernet port and either a second one or WiFi for internet connectivity. &lt;s&gt;A basic script to set up a Linux machine as a router is posted below&lt;/s&gt; (TODO!).

* '''Optionally: A simple network switch, in case you want to add multiple machines to the network. You plug one end into the CGHMN Router box and then your clients can all access CGHMN. Super easy!'''

On the right is an example of what a CGHMN router setup could look like.

=== Get connected - With OpenWRT ===
If you chose to go with an OpenWRT compatible router or want to run OpenWRT on typical x86 hardware/in a VM, you can follow these steps to get yourself connected to the CGHMN:

# Update your OpenWRT install to the latest version to ensure all required packages are available and compatible.
# Download [https://raw.githubusercontent.com/jonasluehrig/cghmn-get-connected/refs/heads/main/openwrt/setup-cghmn.sh this script from GitHub] to your OpenWRT router via SSH
# Run the following commands on the router:
## &lt;code&gt;ash setup-cghmn.sh install-pkgs&lt;/code&gt;
## &lt;code&gt;ash setup-cghmn.sh init&lt;/code&gt;
## You will be asked what network port you'd like to use for the Retro LAN. This is where you will plug in your retro machines to be part of the CGHMN. Choose a port that is not assigned to any OpenWRT interface like '''lan''' or '''wan''' or which not already part of a bridge and enter the Linux interface name, e.g. &lt;code&gt;eth1&lt;/code&gt;, then press &lt;code&gt;[Enter]&lt;/code&gt; to continue. If your router only has two ports and you're using one for WAN, then you first have to [https://openwrt.org/docs/guide-user/luci/luci.secure#allow_access_from_internet enable the web UI and SSH access via the '''wan''' OpenWRT interface], remove the entire '''lan''' OpenWRT interface to free the network port and continue the setup over the IP address your router got on its WAN side. If you only have a single Ethernet port, you're running on a router setup we can't really recommend, however you can configure VLANs and use a managed switch to both get a WAN DHCP address for internet access and have a separate VLAN for the Retro LAN bridge over a single port. This is commonly referred to as "[[wikipedia:Router_on_a_stick|router on a stick]]". Just enter the VLAN interface name here if you choose to go that route.
# Now you will be given some information on the console, including a Wireguard public key. Send one of the CGHMN admins (currently CursedSilicon and Snep) that key so we can add your router to our Wireguard server.
# In return, you will receive a tunnel IPv4 address (&lt;code&gt;100.89.128.x/32&lt;/code&gt;) and a routed IPv4 subnet (&lt;code&gt;100.96.x.0/24&lt;/code&gt;) from us. These will be needed on the third and final step of the setup script:
## &lt;code&gt;ash setup-cghmn.sh set-tunnel-ip&lt;/code&gt;
# Once the script completed successfully, reboot the router to ensure all interfaces are up properly. After the reboot, your retro devices should receive an IP address in your routed IPv4 subnet on the Retro LAN port you chose above and be able to communicate with other machines on the CGHMN network.


=== Get connected - Server Side, the Admins Guide ===
[[File:Example Configuration for new Wireguard Peer on Core Router.png|thumb|Example Configuration for new Wireguard Peer on Core Router]]
To get a member onto the network, they will send an admin of the project their randomly generated Wireguard key during the setup via the OpenWRT script. Here are the steps that admin will have to follow to get them up and running on the server side:

# Log in on the [https://router.core.cghmn:8443 Core Router] over an existing CGHMN network link
# Navigate to VPN -&gt; Wireguard -&gt; Peer Generator
# You will be asked to enter some data for the new peer, enter the following: 
## '''Instance:''' &lt;code&gt;WG_Member&lt;/code&gt;   
## '''Endpoint:''' &lt;code&gt;wg-admin.cursedsilicon.net:42070&lt;/code&gt;
## '''Name:''' &lt;code&gt;member.''&lt;Nickname of the new member&gt;''&lt;/code&gt;
## '''Public Key:''' &lt;code&gt;''&lt;their Wireguard public key they've sent over&gt;''&lt;/code&gt;
## '''Private Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Address:''' ''&lt;code&gt;&lt;Next highest IP from 100.89.128.0/22, this is their tunnel IP and is auto-filled&gt;&lt;/code&gt;''
## '''Pre-Shared Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Allowed IPs:''' &lt;code&gt;''&lt;the same as Address&gt;'', ''&lt;their routed subnet, [[How to Get Connected#But wait, what even is their routed subnet?|see below]]&gt;''&lt;/code&gt;
## '''Keepalive interval:''' ''&lt;code&gt;&lt;blank&gt;&lt;/code&gt;''
## '''DNS Servers:''' &lt;code&gt;''&lt;default value&gt;''&lt;/code&gt;
# Hit the "Store and generate next" button
# Navigate to VPN -&gt; Wireguard -&gt; Instances
# Hit the "Apply" button
# Do either one of these steps, depending on if you can SSH into the GRETAP endpoint container:
## SSH into the CGHMN Proxmox Server and enter the command &lt;code&gt;pct enter 10403&lt;/code&gt;
## SSH directly into the GRETAP endpoint (formerly VXLAN endpoint) container with &lt;code&gt;ssh root@172.23.4.103&lt;/code&gt;
# From there, run the following command: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh &lt;member-tunnel-ip&gt; &lt;member-name&gt;&lt;/code&gt; where you replace &lt;code&gt;&lt;member-tunnel-ip&gt;&lt;/code&gt; with the IP tunnel address of the member as it was set above in the '''Address''' field, without the &lt;code&gt;/32&lt;/code&gt; CIDR subnet mask, and replace the &lt;code&gt;&lt;member-name&gt;&lt;/code&gt; with the same value you've entered above in the '''Name''' field. For example, like this: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh 100.89.128.6 member.snep.test&lt;/code&gt; This will create a GRETAP (and for legacy purposes, a VXLAN) interface and bring them up automagically. ''Ignore the fact it still says "VXLAN" everywhere, it does both.''
# Now you can send the member their Wireguard Tunnel IP and their routed subnet over and they can finish their client-side setup according to the mini-tutorial above.

==== But wait, what even ''is'' their routed subnet? ====
Each members routed subnet comes per default from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IPv4 block and has a &lt;code&gt;/24&lt;/code&gt; mask. This subnet is their "Retro LAN", to which all their retro computers are hooked into via the router of their choosing. By default, NAT is enabled on the routers, so it wouldn't make a difference which subnet is used on the remote end for the retro machines. However, if someone wants to host servers in the CGHMN and doesn't want to do port forwading, they can disable NAT and let other membres directly connect to their machines via this routed subnet.

To get the routed subnet of a member, take the number from the last octet of the Wireguard tunnel IP of a member, say &lt;code&gt;100.89.128.'''6'''&lt;/code&gt;, and put it into the third octet of the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IP block and replace the &lt;code&gt;/13&lt;/code&gt; with &lt;code&gt;/24&lt;/code&gt;, so you get &lt;code&gt;100.96.'''6'''.0/24&lt;/code&gt;. That is their routed subnet, simple as that!</text>
    <sha1>03d449bdda6afb9e04c963c9015bd4150492f902</sha1>
  </revision>
  <revision>
    <id>156</id>
    <parentid>153</parentid>
    <timestamp>2025-05-05T22:30:50Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>Added reminder to add member connection to IP allocations table</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8288" xml:space="preserve">This is a quick and dirty "how do I get on CGHMN" 

Right now since the service is in "closed beta" these steps are a bit vague and manual. But over time as we figure out what works we'll add more connection methods and better documentation

Right now to get connected you effectively need three things, hardware wise:


[[File:CGHMN.png|thumb|319x319px|Example CGHMN Router Setup using a GL-AR300M and basic network switch]]

=== Hardware requirements ===
To connect your retro machine(s) to the CGHMN, you'll need the following:
*'''An Ethernet connection on your retro device(s) of choice, with a TCP/IP (v4) stack for now! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works.'''

* '''Something with the ability to run Wireguard and forward IPv4 packets at the minimum and, for any non-IP packets, &lt;code&gt;gretap&lt;/code&gt; and &lt;code&gt;nftables&lt;/code&gt;. Personally we recommend something running OpenWRT, like the [https://www.gl-inet.com/products/gl-ar300m GL-AR300M] which we have successfully tested to work. We're currently working on a pre-built image for some select routers to make the setup easier for new members. A script to configure already existing OpenWRT instances can be found below.'''
* Alternatively, you can also run the CGHMN routing on any standard Linux box which has at least one Ethernet port and either a second one or WiFi for internet connectivity. &lt;s&gt;A basic script to set up a Linux machine as a router is posted below&lt;/s&gt; (TODO!).

* '''Optionally: A simple network switch, in case you want to add multiple machines to the network. You plug one end into the CGHMN Router box and then your clients can all access CGHMN. Super easy!'''

On the right is an example of what a CGHMN router setup could look like.

=== Get connected - With OpenWRT ===
If you chose to go with an OpenWRT compatible router or want to run OpenWRT on typical x86 hardware/in a VM, you can follow these steps to get yourself connected to the CGHMN:

# Update your OpenWRT install to the latest version to ensure all required packages are available and compatible.
# Download [https://raw.githubusercontent.com/jonasluehrig/cghmn-get-connected/refs/heads/main/openwrt/setup-cghmn.sh this script from GitHub] to your OpenWRT router via SSH
# Run the following commands on the router:
## &lt;code&gt;ash setup-cghmn.sh install-pkgs&lt;/code&gt;
## &lt;code&gt;ash setup-cghmn.sh init&lt;/code&gt;
## You will be asked what network port you'd like to use for the Retro LAN. This is where you will plug in your retro machines to be part of the CGHMN. Choose a port that is not assigned to any OpenWRT interface like '''lan''' or '''wan''' or which not already part of a bridge and enter the Linux interface name, e.g. &lt;code&gt;eth1&lt;/code&gt;, then press &lt;code&gt;[Enter]&lt;/code&gt; to continue. If your router only has two ports and you're using one for WAN, then you first have to [https://openwrt.org/docs/guide-user/luci/luci.secure#allow_access_from_internet enable the web UI and SSH access via the '''wan''' OpenWRT interface], remove the entire '''lan''' OpenWRT interface to free the network port and continue the setup over the IP address your router got on its WAN side. If you only have a single Ethernet port, you're running on a router setup we can't really recommend, however you can configure VLANs and use a managed switch to both get a WAN DHCP address for internet access and have a separate VLAN for the Retro LAN bridge over a single port. This is commonly referred to as "[[wikipedia:Router_on_a_stick|router on a stick]]". Just enter the VLAN interface name here if you choose to go that route.
# Now you will be given some information on the console, including a Wireguard public key. Send one of the CGHMN admins (currently CursedSilicon and Snep) that key so we can add your router to our Wireguard server.
# In return, you will receive a tunnel IPv4 address (&lt;code&gt;100.89.128.x/32&lt;/code&gt;) and a routed IPv4 subnet (&lt;code&gt;100.96.x.0/24&lt;/code&gt;) from us. These will be needed on the third and final step of the setup script:
## &lt;code&gt;ash setup-cghmn.sh set-tunnel-ip&lt;/code&gt;
# Once the script completed successfully, reboot the router to ensure all interfaces are up properly. After the reboot, your retro devices should receive an IP address in your routed IPv4 subnet on the Retro LAN port you chose above and be able to communicate with other machines on the CGHMN network.

&lt;nowiki&gt;#&lt;/nowiki&gt; TODO: Add Linux commands to get connected without OpenWRT
=== Get connected - Server Side, the Admins Guide ===
[[File:Example Configuration for new Wireguard Peer on Core Router.png|thumb|Example Configuration for new Wireguard Peer on Core Router]]
To get a member onto the network, they will send an admin of the project their randomly generated Wireguard key during the setup via the OpenWRT script. Here are the steps that admin will have to follow to get them up and running on the server side:

# Log in on the [https://router.core.cghmn:8443 Core Router] over an existing CGHMN network link
# Navigate to VPN -&gt; Wireguard -&gt; Peer Generator
# You will be asked to enter some data for the new peer, enter the following: 
## '''Instance:''' &lt;code&gt;WG_Member&lt;/code&gt;   
## '''Endpoint:''' &lt;code&gt;wg-admin.cursedsilicon.net:42070&lt;/code&gt;
## '''Name:''' &lt;code&gt;member.''&lt;Nickname of the new member&gt;''&lt;/code&gt;
## '''Public Key:''' &lt;code&gt;''&lt;their Wireguard public key they've sent over&gt;''&lt;/code&gt;
## '''Private Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Address:''' ''&lt;code&gt;&lt;Next highest IP from 100.89.128.0/22, this is their tunnel IP and is auto-filled&gt;&lt;/code&gt;''
## '''Pre-Shared Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Allowed IPs:''' &lt;code&gt;''&lt;the same as Address&gt;'', ''&lt;their routed subnet, [[How to Get Connected#But wait, what even is their routed subnet?|see below]]&gt;''&lt;/code&gt;
## '''Keepalive interval:''' ''&lt;code&gt;&lt;blank&gt;&lt;/code&gt;''
## '''DNS Servers:''' &lt;code&gt;''&lt;default value&gt;''&lt;/code&gt;
# Hit the "Store and generate next" button
# Navigate to VPN -&gt; Wireguard -&gt; Instances
# Hit the "Apply" button
# Do either one of these steps, depending on if you can SSH into the GRETAP endpoint container:
## SSH into the CGHMN Proxmox Server and enter the command &lt;code&gt;pct enter 10403&lt;/code&gt;
## SSH directly into the GRETAP endpoint (formerly VXLAN endpoint) container with &lt;code&gt;ssh root@172.23.4.103&lt;/code&gt;
# From there, run the following command: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh &lt;member-tunnel-ip&gt; &lt;member-name&gt;&lt;/code&gt; where you replace &lt;code&gt;&lt;member-tunnel-ip&gt;&lt;/code&gt; with the IP tunnel address of the member as it was set above in the '''Address''' field, without the &lt;code&gt;/32&lt;/code&gt; CIDR subnet mask, and replace the &lt;code&gt;&lt;member-name&gt;&lt;/code&gt; with the same value you've entered above in the '''Name''' field. For example, like this: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh 100.89.128.6 member.snep.test&lt;/code&gt; This will create a GRETAP (and for legacy purposes, a VXLAN) interface and bring them up automagically. ''Ignore the fact it still says "VXLAN" everywhere, it does both.''
# Now you can send the member their Wireguard Tunnel IP and their routed subnet over and they can finish their client-side setup according to the mini-tutorial above.
# Rember to add the member and their tunnel and subnet IPs to the [[CGHMN-IP-Allocations|IP allocations page]] :)

==== But wait, what even ''is'' their routed subnet? ====
Each members routed subnet comes per default from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IPv4 block and has a &lt;code&gt;/24&lt;/code&gt; mask. This subnet is their "Retro LAN", to which all their retro computers are hooked into via the router of their choosing. By default, NAT is enabled on the routers, so it wouldn't make a difference which subnet is used on the remote end for the retro machines. However, if someone wants to host servers in the CGHMN and doesn't want to do port forwading, they can disable NAT and let other membres directly connect to their machines via this routed subnet.

To get the routed subnet of a member, take the number from the last octet of the Wireguard tunnel IP of a member, say &lt;code&gt;100.89.128.'''6'''&lt;/code&gt;, and put it into the third octet of the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IP block and replace the &lt;code&gt;/13&lt;/code&gt; with &lt;code&gt;/24&lt;/code&gt;, so you get &lt;code&gt;100.96.'''6'''.0/24&lt;/code&gt;. That is their routed subnet, simple as that!</text>
    <sha1>8151839d9442dfbb063ca9de1526dc0af11aed8a</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>File:Example Configuration for new Wireguard Peer on Core Router.png</title>
  <ns>6</ns>
  <id>83</id>
  <revision>
    <id>150</id>
    <timestamp>2025-04-24T01:16:17Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="122" xml:space="preserve">Shows an example of all the values filled in, which are needed to add a new Member Wireguard connection to the Core Router</text>
    <sha1>b08d17001db34a945c6ed9623b02d15fd9ece882</sha1>
  </revision>
</page>
<page arvcontinue="20250214230952|104">
  <title>External Services</title>
  <ns>0</ns>
  <id>84</id>
  <revision>
    <id>154</id>
    <timestamp>2025-04-29T21:39:45Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>WIP</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1231" xml:space="preserve">So! You want to run services on CGHMN. But you also want them to be accessible to the broader internet?

By default the network is designed to be effectively "hermetically sealed". IE: Clients can connect '''''into the network''''' but aren't really meant to have internet access or the ability to talk to "the outside"

This is still "the default" for the innumerable amount of security (and legal!) issues that could arise for the network if we effectively acted as an "open web proxy with extra steps" but that's not a discussion for here! 

Currently the two ways to bridge external services are 

1. '''Run your own gateway!''' We can't really "stop" you from running a proxy to the real internet or other services. We can (and do) '''''heavily suggest against this''''' as anything (and everything) that comes out of it is effectively "your" traffic. 

At the bare minimum you probably want to use some kind of IP whitelisting (both for source and destination) and bandwidth limiting. Anything you can do to minimize harm to yourself the better! 

2. '''Use a middlebox!''' Okay so this isn't much "more" fool-proofed than option #1 but is effectively how we've got the (few) services that warrant internet access configured.</text>
    <sha1>02fe4b016c137a35163772ab63e511253a39dea5</sha1>
  </revision>
</page>
<page arvcontinue="20250506224236|158">
  <title>CGHMN-IP-Allocations</title>
  <ns>0</ns>
  <id>77</id>
  <revision>
    <id>158</id>
    <parentid>157</parentid>
    <timestamp>2025-05-06T22:42:36Z</timestamp>
    <contributor>
      <username>Ilostmybagel</username>
      <id>3</id>
    </contributor>
    <comment>/* Members' Networks */ Put what device I'm using in the Connection Name</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1796" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|MT300n Router
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| -
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| -
|100.89.128.7
|100.96.7.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.100
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|}</text>
    <sha1>6ce4f27242afe52d4d4665d5841785a226c207a5</sha1>
  </revision>
  <revision>
    <id>160</id>
    <parentid>158</parentid>
    <timestamp>2025-05-09T21:13:07Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>Added loganius</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1846" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|MT300n Router
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| -
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| -
|100.89.128.7
|100.96.7.0/24
| -
|-
|Loganius
| -
|100.89.128.8
|100.96.8.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.100
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|}</text>
    <sha1>08365bb731cd0c27867c6e9f2558d4bcc1e39fd5</sha1>
  </revision>
  <revision>
    <id>161</id>
    <parentid>160</parentid>
    <timestamp>2025-05-09T21:14:02Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1862" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| -
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| -
|100.89.128.7
|100.96.7.0/24
| -
|-
|Loganius
| -
|100.89.128.8
|100.96.8.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.100
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|}</text>
    <sha1>00856edd00f1b44805a3063982e42435bd364cdb</sha1>
  </revision>
  <revision>
    <id>162</id>
    <parentid>161</parentid>
    <timestamp>2025-05-09T21:20:17Z</timestamp>
    <contributor>
      <username>Ilostmybagel</username>
      <id>3</id>
    </contributor>
    <comment>/* Members' Networks */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1869" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| -
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge r620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| -
|100.89.128.7
|100.96.7.0/24
| -
|-
|Loganius
| -
|100.89.128.8
|100.96.8.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.100
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|}</text>
    <sha1>90281f86ca584274e776852e50c4284ccf0ce7a5</sha1>
  </revision>
  <revision>
    <id>163</id>
    <parentid>162</parentid>
    <timestamp>2025-05-09T21:31:41Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>Added Lily Hosting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1921" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| -
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge r620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| -
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Hosting
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| -
|100.89.128.9
|100.96.9.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.100
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|}</text>
    <sha1>b1a3b0e5ba3b52bc4dfac0ac4da2e7e831d121a6</sha1>
  </revision>
  <revision>
    <id>164</id>
    <parentid>163</parentid>
    <timestamp>2025-05-09T23:33:47Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>Added GothPanda</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1974" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| -
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge r620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| -
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Hosting
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| -
|100.89.128.9
|100.96.9.0/24
| -
|-
|GothPanda
| -
|100.89.128.10
|100.96.10.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.100
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|}</text>
    <sha1>f9ed2d62ccda0f02f5215329439990e9c12c4506</sha1>
  </revision>
  <revision>
    <id>165</id>
    <parentid>164</parentid>
    <timestamp>2025-05-11T00:27:53Z</timestamp>
    <contributor>
      <username>Ilostmybagel</username>
      <id>3</id>
    </contributor>
    <comment>/* Member-Delegated (Sub-) Domains */ Added lily.retro to the member-delegated domains</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2029" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| -
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge r620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| -
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Hosting
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| -
|100.89.128.9
|100.96.9.0/24
| -
|-
|GothPanda
| -
|100.89.128.10
|100.96.10.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.100
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|}</text>
    <sha1>7dc759fc0f7ec37d7b759a51479c301f95df8ef1</sha1>
  </revision>
  <revision>
    <id>176</id>
    <parentid>165</parentid>
    <timestamp>2025-05-15T21:56:16Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Added my domain to the list of member delegated subdomains.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2106" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| -
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge r620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| -
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Hosting
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| -
|100.89.128.9
|100.96.9.0/24
| -
|-
|GothPanda
| -
|100.89.128.10
|100.96.10.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.100
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|loganius-win2k3.loganius.retro
|100.96.9.1
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|}</text>
    <sha1>1ba90e61c848e3f72f1d6e88d00ba5d3563319ef</sha1>
  </revision>
  <revision>
    <id>184</id>
    <parentid>176</parentid>
    <timestamp>2025-05-17T15:12:47Z</timestamp>
    <contributor>
      <username>Talija</username>
      <id>10</id>
    </contributor>
    <minor/>
    <comment>Updated for kat.gorl and added category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2270" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| -
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge r620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| -
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Hosting
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| -
|100.89.128.9
|100.96.9.0/24
| -
|-
|GothPanda
| -
|100.89.128.10
|100.96.10.0/24
| -
|-
|kat.gorl
| -
|100.89.128.11
|100.96.11.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.100
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|loganius-win2k3.loganius.retro
|100.96.9.1
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>6385fbbce392a7ef87f4b4c99bc94e26f3d17df4</sha1>
  </revision>
  <revision>
    <id>185</id>
    <parentid>184</parentid>
    <timestamp>2025-05-17T15:15:35Z</timestamp>
    <contributor>
      <username>Talija</username>
      <id>10</id>
    </contributor>
    <comment>/* Member-Delegated (Sub-) Domains */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2354" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| -
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge r620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| -
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Hosting
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| -
|100.89.128.9
|100.96.9.0/24
| -
|-
|GothPanda
| -
|100.89.128.10
|100.96.10.0/24
| -
|-
|kat.gorl
| -
|100.89.128.11
|100.96.11.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|loganius-win2k3.loganius.retro
|100.96.9.1
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
|`
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>6ff780fd1f84f08ad043b54285ca595cfc735e27</sha1>
  </revision>
  <revision>
    <id>186</id>
    <parentid>185</parentid>
    <timestamp>2025-05-18T03:04:54Z</timestamp>
    <contributor>
      <username>Talija</username>
      <id>10</id>
    </contributor>
    <minor/>
    <comment>updated ch0ccyra1n's name (was kat.gorl)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2356" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| -
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge r620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| -
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Hosting
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| -
|100.89.128.9
|100.96.9.0/24
| -
|-
|GothPanda
| -
|100.89.128.10
|100.96.10.0/24
| -
|-
|ch0ccyra1n
| -
|100.89.128.11
|100.96.11.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|loganius-win2k3.loganius.retro
|100.96.9.1
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
|`
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>ce7d75b42265147bfdfd933de8e8ebae25c2352d</sha1>
  </revision>
  <revision>
    <id>187</id>
    <parentid>186</parentid>
    <timestamp>2025-05-18T03:10:02Z</timestamp>
    <contributor>
      <username>Ilostmybagel</username>
      <id>3</id>
    </contributor>
    <comment>/* Members' Networks */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2361" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| -
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| -
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| -
|100.89.128.9
|100.96.9.0/24
| -
|-
|GothPanda
| -
|100.89.128.10
|100.96.10.0/24
| -
|-
|ch0ccyra1n
| -
|100.89.128.11
|100.96.11.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|loganius-win2k3.loganius.retro
|100.96.9.1
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
|`
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>854331a88aff2893699f24bb930f21df38fd7850</sha1>
  </revision>
  <revision>
    <id>189</id>
    <parentid>187</parentid>
    <timestamp>2025-05-25T05:30:32Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Update my DNS info</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2353" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection Name
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|AR300 Router
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| -
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| -
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| -
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| -
|100.89.128.9
|100.96.9.0/24
| -
|-
|GothPanda
| -
|100.89.128.10
|100.96.10.0/24
| -
|-
|ch0ccyra1n
| -
|100.89.128.11
|100.96.11.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>31f76d2ff0ae3480b7f6c4f20790f01d048fb5a6</sha1>
  </revision>
  <revision>
    <id>190</id>
    <parentid>189</parentid>
    <timestamp>2025-05-25T05:50:40Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Added Chromaryu</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2450" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection "Method"
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| Unknown
|100.89.128.9
|100.96.9.0/24
| -
|-
|GothPanda
| Unknown
|100.89.128.10
|100.96.10.0/24
| -
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>d51495555c8dcc645774ca672781b71f8145ff47</sha1>
  </revision>
  <revision>
    <id>191</id>
    <parentid>190</parentid>
    <timestamp>2025-05-25T05:58:10Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Added my connection method.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2528" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Connection "Method"
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| Unknown
|100.89.128.10
|100.96.10.0/24
| -
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|Snep
|snep.retro
|ns1.snep.retro
|172.23.8.11
| -
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>aa54c6f9c72cbff9eb57e2823c1e3ed0b5fbc3d8</sha1>
  </revision>
  <revision>
    <id>192</id>
    <parentid>191</parentid>
    <timestamp>2025-05-25T21:33:01Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2558" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| Unknown
|100.89.128.10
|100.96.10.0/24
| -
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>70208bb69a21a5b5b7814e849a69ed24bb270fd7</sha1>
  </revision>
  <revision>
    <id>195</id>
    <parentid>192</parentid>
    <timestamp>2025-05-31T04:48:51Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Added devhack IP range</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2714" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| Unknown
|100.89.128.10
|100.96.10.0/24
| -
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>d071e3e377dff0dc54089aad3b83157f0dbcd2c1</sha1>
  </revision>
  <revision>
    <id>207</id>
    <parentid>195</parentid>
    <timestamp>2025-06-06T09:01:17Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2773" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| Unknown
|100.89.128.10
|100.96.10.0/24
| -
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>ade21dcb0acf1d9ae0a8a657a0ccda261991f07e</sha1>
  </revision>
</page>
<page arvcontinue="20250506224236|158">
  <title>How to Get Connected</title>
  <ns>0</ns>
  <id>82</id>
  <revision>
    <id>159</id>
    <parentid>156</parentid>
    <timestamp>2025-05-07T04:26:09Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>Added short Get Connected for manual Wireguard connections</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10215" xml:space="preserve">This is a quick and dirty "how do I get on CGHMN" 

Right now since the service is in "closed beta" these steps are a bit vague and manual. But over time as we figure out what works we'll add more connection methods and better documentation

Right now to get connected you effectively need three things, hardware wise:


[[File:CGHMN.png|thumb|319x319px|Example CGHMN Router Setup using a GL-AR300M and basic network switch]]

=== Hardware requirements ===
To connect your retro machine(s) to the CGHMN, you'll need the following:
*'''An Ethernet connection on your retro device(s) of choice, with a TCP/IP (v4) stack for now! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works.'''

* '''Something with the ability to run Wireguard and forward IPv4 packets at the minimum and, for any non-IP packets, &lt;code&gt;gretap&lt;/code&gt; and &lt;code&gt;nftables&lt;/code&gt;. Personally we recommend something running OpenWRT, like the [https://www.gl-inet.com/products/gl-ar300m GL-AR300M] which we have successfully tested to work. We're currently working on a pre-built image for some select routers to make the setup easier for new members. A script to configure already existing OpenWRT instances can be found below.'''
* Alternatively, you can also run the CGHMN routing on any standard Linux box which has at least one Ethernet port and either a second one or WiFi for internet connectivity. &lt;s&gt;A basic script to set up a Linux machine as a router is posted below&lt;/s&gt; (TODO!).

* '''Optionally: A simple network switch, in case you want to add multiple machines to the network. You plug one end into the CGHMN Router box and then your clients can all access CGHMN. Super easy!'''

On the right is an example of what a CGHMN router setup could look like.

=== Get connected - With OpenWRT ===
If you chose to go with an OpenWRT compatible router or want to run OpenWRT on typical x86 hardware/in a VM, you can follow these steps to get yourself connected to the CGHMN:

# Update your OpenWRT install to the latest version to ensure all required packages are available and compatible.
# Download [https://raw.githubusercontent.com/jonasluehrig/cghmn-get-connected/refs/heads/main/openwrt/setup-cghmn.sh this script from GitHub] to your OpenWRT router via SSH
# Run the following commands on the router:
## &lt;code&gt;ash setup-cghmn.sh install-pkgs&lt;/code&gt;
## &lt;code&gt;ash setup-cghmn.sh init&lt;/code&gt;
## You will be asked what network port you'd like to use for the Retro LAN. This is where you will plug in your retro machines to be part of the CGHMN. Choose a port that is not assigned to any OpenWRT interface like '''lan''' or '''wan''' or which not already part of a bridge and enter the Linux interface name, e.g. &lt;code&gt;eth1&lt;/code&gt;, then press &lt;code&gt;[Enter]&lt;/code&gt; to continue. If your router only has two ports and you're using one for WAN, then you first have to [https://openwrt.org/docs/guide-user/luci/luci.secure#allow_access_from_internet enable the web UI and SSH access via the '''wan''' OpenWRT interface], remove the entire '''lan''' OpenWRT interface to free the network port and continue the setup over the IP address your router got on its WAN side. If you only have a single Ethernet port, you're running on a router setup we can't really recommend, however you can configure VLANs and use a managed switch to both get a WAN DHCP address for internet access and have a separate VLAN for the Retro LAN bridge over a single port. This is commonly referred to as "[[wikipedia:Router_on_a_stick|router on a stick]]". Just enter the VLAN interface name here if you choose to go that route.
# Now you will be given some information on the console, including a Wireguard public key. Send one of the CGHMN admins (currently CursedSilicon and Snep) that key so we can add your router to our Wireguard server.
# In return, you will receive a tunnel IPv4 address (&lt;code&gt;100.89.128.x/32&lt;/code&gt;) and a routed IPv4 subnet (&lt;code&gt;100.96.x.0/24&lt;/code&gt;) from us. These will be needed on the third and final step of the setup script:
## &lt;code&gt;ash setup-cghmn.sh set-tunnel-ip&lt;/code&gt;
# Once the script completed successfully, reboot the router to ensure all interfaces are up properly. After the reboot, your retro devices should receive an IP address in your routed IPv4 subnet on the Retro LAN port you chose above and be able to communicate with other machines on the CGHMN network.

=== Get Connected - Manually (Linux, Wireguard only, GRETAP follows shortly) ===
In case you want to setup a connection into the network manually, here are the required steps and information you should be needing:

* Generate a Wireguard private key and public key, this command writes a fresh Wireguard private key to &lt;code&gt;private-key&lt;/code&gt; and the corresponsing public key to &lt;code&gt;public-key&lt;/code&gt;:

 $ wg genkey | tee private-key | wg pubkey &gt; public-key

* NEVER share your private key, even with us! It should never be required outside of your own Wireguard setup!
* You will, however, need to share your public key with us. Send CursedSilicon or Snep on the Discord or via IRC a message including the public key and we'll add you to the tunnel.
* In return, you'll get two IP addresses from us: Your tunnel IP address, with which your router talks to our router, and a routed subnet, from which you can assign IPs to your own machines so they can talk to other CGHMN member devices on the network without NAT in the way.
* Next, you'll need to fill a Wireguard configuration file with the two IP addresses, like below:

 [Interface]
 PrivateKey = &lt;Your private key goes here&gt;
 Address = &lt;Your tunnel IP address goes here&gt;/32
 DNS = 100.89.128.0
 MTU = 1420
 
 [Peer]
 PublicKey = k/QiJIbMakMKgTCHVt8/D+8k4DzRVM6U33F3gMZfRUg=
 Endpoint = wg-admin.cursedsilicon.net:42070
 AllowedIPs = 172.23.0.0/16, 100.89.128.0/22, 100.96.0.0/13
 PersistentKeepalive = 15

* Save this file as &lt;code&gt;wg-cghmn.conf&lt;/code&gt;, for example.
* Then, run &lt;code&gt;wg-quick up ./wg-cghmn.conf&lt;/code&gt;, perhaps requiring &lt;code&gt;doas&lt;/code&gt;/&lt;code&gt;sudo&lt;/code&gt;, to bring the tunnel up and connect to the network!

This should bring whatever system you've set the tunnel up on onto the network and is now reachable for other members on the network, as long as the firewall on your device is congfigured accordingly, of course.

&lt;nowiki&gt;#&lt;/nowiki&gt;TODO: Add example of routed subnet configuration, perhaps on a different Wiki site

=== Get connected - Server Side, the Admins Guide ===
[[File:Example Configuration for new Wireguard Peer on Core Router.png|thumb|Example Configuration for new Wireguard Peer on Core Router]]
To get a member onto the network, they will send an admin of the project their randomly generated Wireguard key during the setup via the OpenWRT script. Here are the steps that admin will have to follow to get them up and running on the server side:

# Log in on the [https://router.core.cghmn:8443 Core Router] over an existing CGHMN network link
# Navigate to VPN -&gt; Wireguard -&gt; Peer Generator
# You will be asked to enter some data for the new peer, enter the following: 
## '''Instance:''' &lt;code&gt;WG_Member&lt;/code&gt;   
## '''Endpoint:''' &lt;code&gt;wg-admin.cursedsilicon.net:42070&lt;/code&gt;
## '''Name:''' &lt;code&gt;member.''&lt;Nickname of the new member&gt;''&lt;/code&gt;
## '''Public Key:''' &lt;code&gt;''&lt;their Wireguard public key they've sent over&gt;''&lt;/code&gt;
## '''Private Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Address:''' ''&lt;code&gt;&lt;Next highest IP from 100.89.128.0/22, this is their tunnel IP and is auto-filled&gt;&lt;/code&gt;''
## '''Pre-Shared Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Allowed IPs:''' &lt;code&gt;''&lt;the same as Address&gt;'', ''&lt;their routed subnet, [[How to Get Connected#But wait, what even is their routed subnet?|see below]]&gt;''&lt;/code&gt;
## '''Keepalive interval:''' ''&lt;code&gt;&lt;blank&gt;&lt;/code&gt;''
## '''DNS Servers:''' &lt;code&gt;''&lt;default value&gt;''&lt;/code&gt;
# Hit the "Store and generate next" button
# Navigate to VPN -&gt; Wireguard -&gt; Instances
# Hit the "Apply" button
# Do either one of these steps, depending on if you can SSH into the GRETAP endpoint container:
## SSH into the CGHMN Proxmox Server and enter the command &lt;code&gt;pct enter 10403&lt;/code&gt;
## SSH directly into the GRETAP endpoint (formerly VXLAN endpoint) container with &lt;code&gt;ssh root@172.23.4.103&lt;/code&gt;
# From there, run the following command: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh &lt;member-tunnel-ip&gt; &lt;member-name&gt;&lt;/code&gt; where you replace &lt;code&gt;&lt;member-tunnel-ip&gt;&lt;/code&gt; with the IP tunnel address of the member as it was set above in the '''Address''' field, without the &lt;code&gt;/32&lt;/code&gt; CIDR subnet mask, and replace the &lt;code&gt;&lt;member-name&gt;&lt;/code&gt; with the same value you've entered above in the '''Name''' field. For example, like this: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh 100.89.128.6 member.snep.test&lt;/code&gt; This will create a GRETAP (and for legacy purposes, a VXLAN) interface and bring them up automagically. ''Ignore the fact it still says "VXLAN" everywhere, it does both.''
# Now you can send the member their Wireguard Tunnel IP and their routed subnet over and they can finish their client-side setup according to the mini-tutorial above.
# Rember to add the member and their tunnel and subnet IPs to the [[CGHMN-IP-Allocations|IP allocations page]] :)

==== But wait, what even ''is'' their routed subnet? ====
Each members routed subnet comes per default from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IPv4 block and has a &lt;code&gt;/24&lt;/code&gt; mask. This subnet is their "Retro LAN", to which all their retro computers are hooked into via the router of their choosing. By default, NAT is enabled on the routers, so it wouldn't make a difference which subnet is used on the remote end for the retro machines. However, if someone wants to host servers in the CGHMN and doesn't want to do port forwading, they can disable NAT and let other membres directly connect to their machines via this routed subnet.

To get the routed subnet of a member, take the number from the last octet of the Wireguard tunnel IP of a member, say &lt;code&gt;100.89.128.'''6'''&lt;/code&gt;, and put it into the third octet of the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IP block and replace the &lt;code&gt;/13&lt;/code&gt; with &lt;code&gt;/24&lt;/code&gt;, so you get &lt;code&gt;100.96.'''6'''.0/24&lt;/code&gt;. That is their routed subnet, simple as that!</text>
    <sha1>a0f6fdb4f84b5afb8b38f398ec20e9168ade2fba</sha1>
  </revision>
  <revision>
    <id>170</id>
    <parentid>159</parentid>
    <timestamp>2025-05-11T02:33:31Z</timestamp>
    <contributor>
      <username>Ilostmybagel</username>
      <id>3</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10256" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
This is a quick and dirty "how do I get on CGHMN" 

Right now since the service is in "closed beta" these steps are a bit vague and manual. But over time as we figure out what works we'll add more connection methods and better documentation

Right now to get connected you effectively need three things, hardware wise:


[[File:CGHMN.png|thumb|319x319px|Example CGHMN Router Setup using a GL-AR300M and basic network switch]]

=== Hardware requirements ===
To connect your retro machine(s) to the CGHMN, you'll need the following:
*'''An Ethernet connection on your retro device(s) of choice, with a TCP/IP (v4) stack for now! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works.'''

* '''Something with the ability to run Wireguard and forward IPv4 packets at the minimum and, for any non-IP packets, &lt;code&gt;gretap&lt;/code&gt; and &lt;code&gt;nftables&lt;/code&gt;. Personally we recommend something running OpenWRT, like the [https://www.gl-inet.com/products/gl-ar300m GL-AR300M] which we have successfully tested to work. We're currently working on a pre-built image for some select routers to make the setup easier for new members. A script to configure already existing OpenWRT instances can be found below.'''
* Alternatively, you can also run the CGHMN routing on any standard Linux box which has at least one Ethernet port and either a second one or WiFi for internet connectivity. &lt;s&gt;A basic script to set up a Linux machine as a router is posted below&lt;/s&gt; (TODO!).

* '''Optionally: A simple network switch, in case you want to add multiple machines to the network. You plug one end into the CGHMN Router box and then your clients can all access CGHMN. Super easy!'''

On the right is an example of what a CGHMN router setup could look like.

=== Get connected - With OpenWRT ===
If you chose to go with an OpenWRT compatible router or want to run OpenWRT on typical x86 hardware/in a VM, you can follow these steps to get yourself connected to the CGHMN:

# Update your OpenWRT install to the latest version to ensure all required packages are available and compatible.
# Download [https://raw.githubusercontent.com/jonasluehrig/cghmn-get-connected/refs/heads/main/openwrt/setup-cghmn.sh this script from GitHub] to your OpenWRT router via SSH
# Run the following commands on the router:
## &lt;code&gt;ash setup-cghmn.sh install-pkgs&lt;/code&gt;
## &lt;code&gt;ash setup-cghmn.sh init&lt;/code&gt;
## You will be asked what network port you'd like to use for the Retro LAN. This is where you will plug in your retro machines to be part of the CGHMN. Choose a port that is not assigned to any OpenWRT interface like '''lan''' or '''wan''' or which not already part of a bridge and enter the Linux interface name, e.g. &lt;code&gt;eth1&lt;/code&gt;, then press &lt;code&gt;[Enter]&lt;/code&gt; to continue. If your router only has two ports and you're using one for WAN, then you first have to [https://openwrt.org/docs/guide-user/luci/luci.secure#allow_access_from_internet enable the web UI and SSH access via the '''wan''' OpenWRT interface], remove the entire '''lan''' OpenWRT interface to free the network port and continue the setup over the IP address your router got on its WAN side. If you only have a single Ethernet port, you're running on a router setup we can't really recommend, however you can configure VLANs and use a managed switch to both get a WAN DHCP address for internet access and have a separate VLAN for the Retro LAN bridge over a single port. This is commonly referred to as "[[wikipedia:Router_on_a_stick|router on a stick]]". Just enter the VLAN interface name here if you choose to go that route.
# Now you will be given some information on the console, including a Wireguard public key. Send one of the CGHMN admins (currently CursedSilicon and Snep) that key so we can add your router to our Wireguard server.
# In return, you will receive a tunnel IPv4 address (&lt;code&gt;100.89.128.x/32&lt;/code&gt;) and a routed IPv4 subnet (&lt;code&gt;100.96.x.0/24&lt;/code&gt;) from us. These will be needed on the third and final step of the setup script:
## &lt;code&gt;ash setup-cghmn.sh set-tunnel-ip&lt;/code&gt;
# Once the script completed successfully, reboot the router to ensure all interfaces are up properly. After the reboot, your retro devices should receive an IP address in your routed IPv4 subnet on the Retro LAN port you chose above and be able to communicate with other machines on the CGHMN network.

=== Get Connected - Manually (Linux, Wireguard only, GRETAP follows shortly) ===
In case you want to setup a connection into the network manually, here are the required steps and information you should be needing:

* Generate a Wireguard private key and public key, this command writes a fresh Wireguard private key to &lt;code&gt;private-key&lt;/code&gt; and the corresponsing public key to &lt;code&gt;public-key&lt;/code&gt;:

 $ wg genkey | tee private-key | wg pubkey &gt; public-key

* NEVER share your private key, even with us! It should never be required outside of your own Wireguard setup!
* You will, however, need to share your public key with us. Send CursedSilicon or Snep on the Discord or via IRC a message including the public key and we'll add you to the tunnel.
* In return, you'll get two IP addresses from us: Your tunnel IP address, with which your router talks to our router, and a routed subnet, from which you can assign IPs to your own machines so they can talk to other CGHMN member devices on the network without NAT in the way.
* Next, you'll need to fill a Wireguard configuration file with the two IP addresses, like below:

 [Interface]
 PrivateKey = &lt;Your private key goes here&gt;
 Address = &lt;Your tunnel IP address goes here&gt;/32
 DNS = 100.89.128.0
 MTU = 1420
 
 [Peer]
 PublicKey = k/QiJIbMakMKgTCHVt8/D+8k4DzRVM6U33F3gMZfRUg=
 Endpoint = wg-admin.cursedsilicon.net:42070
 AllowedIPs = 172.23.0.0/16, 100.89.128.0/22, 100.96.0.0/13
 PersistentKeepalive = 15

* Save this file as &lt;code&gt;wg-cghmn.conf&lt;/code&gt;, for example.
* Then, run &lt;code&gt;wg-quick up ./wg-cghmn.conf&lt;/code&gt;, perhaps requiring &lt;code&gt;doas&lt;/code&gt;/&lt;code&gt;sudo&lt;/code&gt;, to bring the tunnel up and connect to the network!

This should bring whatever system you've set the tunnel up on onto the network and is now reachable for other members on the network, as long as the firewall on your device is congfigured accordingly, of course.

&lt;nowiki&gt;#&lt;/nowiki&gt;TODO: Add example of routed subnet configuration, perhaps on a different Wiki site

=== Get connected - Server Side, the Admins Guide ===
[[File:Example Configuration for new Wireguard Peer on Core Router.png|thumb|Example Configuration for new Wireguard Peer on Core Router]]
To get a member onto the network, they will send an admin of the project their randomly generated Wireguard key during the setup via the OpenWRT script. Here are the steps that admin will have to follow to get them up and running on the server side:

# Log in on the [https://router.core.cghmn:8443 Core Router] over an existing CGHMN network link
# Navigate to VPN -&gt; Wireguard -&gt; Peer Generator
# You will be asked to enter some data for the new peer, enter the following: 
## '''Instance:''' &lt;code&gt;WG_Member&lt;/code&gt;   
## '''Endpoint:''' &lt;code&gt;wg-admin.cursedsilicon.net:42070&lt;/code&gt;
## '''Name:''' &lt;code&gt;member.''&lt;Nickname of the new member&gt;''&lt;/code&gt;
## '''Public Key:''' &lt;code&gt;''&lt;their Wireguard public key they've sent over&gt;''&lt;/code&gt;
## '''Private Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Address:''' ''&lt;code&gt;&lt;Next highest IP from 100.89.128.0/22, this is their tunnel IP and is auto-filled&gt;&lt;/code&gt;''
## '''Pre-Shared Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Allowed IPs:''' &lt;code&gt;''&lt;the same as Address&gt;'', ''&lt;their routed subnet, [[How to Get Connected#But wait, what even is their routed subnet?|see below]]&gt;''&lt;/code&gt;
## '''Keepalive interval:''' ''&lt;code&gt;&lt;blank&gt;&lt;/code&gt;''
## '''DNS Servers:''' &lt;code&gt;''&lt;default value&gt;''&lt;/code&gt;
# Hit the "Store and generate next" button
# Navigate to VPN -&gt; Wireguard -&gt; Instances
# Hit the "Apply" button
# Do either one of these steps, depending on if you can SSH into the GRETAP endpoint container:
## SSH into the CGHMN Proxmox Server and enter the command &lt;code&gt;pct enter 10403&lt;/code&gt;
## SSH directly into the GRETAP endpoint (formerly VXLAN endpoint) container with &lt;code&gt;ssh root@172.23.4.103&lt;/code&gt;
# From there, run the following command: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh &lt;member-tunnel-ip&gt; &lt;member-name&gt;&lt;/code&gt; where you replace &lt;code&gt;&lt;member-tunnel-ip&gt;&lt;/code&gt; with the IP tunnel address of the member as it was set above in the '''Address''' field, without the &lt;code&gt;/32&lt;/code&gt; CIDR subnet mask, and replace the &lt;code&gt;&lt;member-name&gt;&lt;/code&gt; with the same value you've entered above in the '''Name''' field. For example, like this: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh 100.89.128.6 member.snep.test&lt;/code&gt; This will create a GRETAP (and for legacy purposes, a VXLAN) interface and bring them up automagically. ''Ignore the fact it still says "VXLAN" everywhere, it does both.''
# Now you can send the member their Wireguard Tunnel IP and their routed subnet over and they can finish their client-side setup according to the mini-tutorial above.
# Rember to add the member and their tunnel and subnet IPs to the [[CGHMN-IP-Allocations|IP allocations page]] :)

==== But wait, what even ''is'' their routed subnet? ====
Each members routed subnet comes per default from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IPv4 block and has a &lt;code&gt;/24&lt;/code&gt; mask. This subnet is their "Retro LAN", to which all their retro computers are hooked into via the router of their choosing. By default, NAT is enabled on the routers, so it wouldn't make a difference which subnet is used on the remote end for the retro machines. However, if someone wants to host servers in the CGHMN and doesn't want to do port forwading, they can disable NAT and let other membres directly connect to their machines via this routed subnet.

To get the routed subnet of a member, take the number from the last octet of the Wireguard tunnel IP of a member, say &lt;code&gt;100.89.128.'''6'''&lt;/code&gt;, and put it into the third octet of the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IP block and replace the &lt;code&gt;/13&lt;/code&gt; with &lt;code&gt;/24&lt;/code&gt;, so you get &lt;code&gt;100.96.'''6'''.0/24&lt;/code&gt;. That is their routed subnet, simple as that!</text>
    <sha1>11c765bb0983927c8b828da3f06c9f816e7e447a</sha1>
  </revision>
  <revision>
    <id>173</id>
    <parentid>170</parentid>
    <timestamp>2025-05-12T09:05:35Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Added link to Signup page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10340" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
This is a quick and dirty "how do I get on CGHMN" 

'''Since the service is in "closed beta" these steps are a bit vague and manual. But over time as we figure out what works we'll add more connection methods and better documentation'''

=== Step 1: ===
[[Signup|'''Let us know you'd like to connect!''']] 

(We'll need information from you such as your Wireguard Pubkey to let you connect to the network)[[File:CGHMN.png|thumb|319x319px|Example CGHMN Router Setup using a GL-AR300M and basic network switch]]

=== Hardware requirements ===
To connect your retro machine(s) to the CGHMN, you'll need the following:
*'''An Ethernet connection on your retro device(s) of choice, with a TCP/IP (v4) stack for now! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works.'''

* '''Something with the ability to run Wireguard and forward IPv4 packets at the minimum and, for any non-IP packets, &lt;code&gt;gretap&lt;/code&gt; and &lt;code&gt;nftables&lt;/code&gt;. Personally we recommend something running OpenWRT, like the [https://www.gl-inet.com/products/gl-ar300m GL-AR300M] which we have successfully tested to work. We're currently working on a pre-built image for some select routers to make the setup easier for new members. A script to configure already existing OpenWRT instances can be found below.'''
* Alternatively, you can also run the CGHMN routing on any standard Linux box which has at least one Ethernet port and either a second one or WiFi for internet connectivity. &lt;s&gt;A basic script to set up a Linux machine as a router is posted below&lt;/s&gt; (TODO!).

* '''Optionally: A simple network switch, in case you want to add multiple machines to the network. You plug one end into the CGHMN Router box and then your clients can all access CGHMN. Super easy!'''

On the right is an example of what a CGHMN router setup could look like.

=== Get connected - With OpenWRT ===
If you chose to go with an OpenWRT compatible router or want to run OpenWRT on typical x86 hardware/in a VM, you can follow these steps to get yourself connected to the CGHMN:

# Update your OpenWRT install to the latest version to ensure all required packages are available and compatible.
# Download [https://raw.githubusercontent.com/jonasluehrig/cghmn-get-connected/refs/heads/main/openwrt/setup-cghmn.sh this script from GitHub] to your OpenWRT router via SSH
# Run the following commands on the router:
## &lt;code&gt;ash setup-cghmn.sh install-pkgs&lt;/code&gt;
## &lt;code&gt;ash setup-cghmn.sh init&lt;/code&gt;
## You will be asked what network port you'd like to use for the Retro LAN. This is where you will plug in your retro machines to be part of the CGHMN. Choose a port that is not assigned to any OpenWRT interface like '''lan''' or '''wan''' or which not already part of a bridge and enter the Linux interface name, e.g. &lt;code&gt;eth1&lt;/code&gt;, then press &lt;code&gt;[Enter]&lt;/code&gt; to continue. If your router only has two ports and you're using one for WAN, then you first have to [https://openwrt.org/docs/guide-user/luci/luci.secure#allow_access_from_internet enable the web UI and SSH access via the '''wan''' OpenWRT interface], remove the entire '''lan''' OpenWRT interface to free the network port and continue the setup over the IP address your router got on its WAN side. If you only have a single Ethernet port, you're running on a router setup we can't really recommend, however you can configure VLANs and use a managed switch to both get a WAN DHCP address for internet access and have a separate VLAN for the Retro LAN bridge over a single port. This is commonly referred to as "[[wikipedia:Router_on_a_stick|router on a stick]]". Just enter the VLAN interface name here if you choose to go that route.
# Now you will be given some information on the console, including a Wireguard public key. Send one of the CGHMN admins (currently CursedSilicon and Snep) that key so we can add your router to our Wireguard server.
# In return, you will receive a tunnel IPv4 address (&lt;code&gt;100.89.128.x/32&lt;/code&gt;) and a routed IPv4 subnet (&lt;code&gt;100.96.x.0/24&lt;/code&gt;) from us. These will be needed on the third and final step of the setup script:
## &lt;code&gt;ash setup-cghmn.sh set-tunnel-ip&lt;/code&gt;
# Once the script completed successfully, reboot the router to ensure all interfaces are up properly. After the reboot, your retro devices should receive an IP address in your routed IPv4 subnet on the Retro LAN port you chose above and be able to communicate with other machines on the CGHMN network.

=== Get Connected - Manually (Linux, Wireguard only, GRETAP follows shortly) ===
In case you want to setup a connection into the network manually, here are the required steps and information you should be needing:

* Generate a Wireguard private key and public key, this command writes a fresh Wireguard private key to &lt;code&gt;private-key&lt;/code&gt; and the corresponsing public key to &lt;code&gt;public-key&lt;/code&gt;:

 $ wg genkey | tee private-key | wg pubkey &gt; public-key

* NEVER share your private key, even with us! It should never be required outside of your own Wireguard setup!
* You will, however, need to share your public key with us. Send CursedSilicon or Snep on the Discord or via IRC a message including the public key and we'll add you to the tunnel.
* In return, you'll get two IP addresses from us: Your tunnel IP address, with which your router talks to our router, and a routed subnet, from which you can assign IPs to your own machines so they can talk to other CGHMN member devices on the network without NAT in the way.
* Next, you'll need to fill a Wireguard configuration file with the two IP addresses, like below:

 [Interface]
 PrivateKey = &lt;Your private key goes here&gt;
 Address = &lt;Your tunnel IP address goes here&gt;/32
 DNS = 100.89.128.0
 MTU = 1420
 
 [Peer]
 PublicKey = k/QiJIbMakMKgTCHVt8/D+8k4DzRVM6U33F3gMZfRUg=
 Endpoint = wg-admin.cursedsilicon.net:42070
 AllowedIPs = 172.23.0.0/16, 100.89.128.0/22, 100.96.0.0/13
 PersistentKeepalive = 15

* Save this file as &lt;code&gt;wg-cghmn.conf&lt;/code&gt;, for example.
* Then, run &lt;code&gt;wg-quick up ./wg-cghmn.conf&lt;/code&gt;, perhaps requiring &lt;code&gt;doas&lt;/code&gt;/&lt;code&gt;sudo&lt;/code&gt;, to bring the tunnel up and connect to the network!

This should bring whatever system you've set the tunnel up on onto the network and is now reachable for other members on the network, as long as the firewall on your device is congfigured accordingly, of course.

&lt;nowiki&gt;#&lt;/nowiki&gt;TODO: Add example of routed subnet configuration, perhaps on a different Wiki site

=== Get connected - Server Side, the Admins Guide ===
[[File:Example Configuration for new Wireguard Peer on Core Router.png|thumb|Example Configuration for new Wireguard Peer on Core Router]]
To get a member onto the network, they will send an admin of the project their randomly generated Wireguard key during the setup via the OpenWRT script. Here are the steps that admin will have to follow to get them up and running on the server side:

# Log in on the [https://router.core.cghmn:8443 Core Router] over an existing CGHMN network link
# Navigate to VPN -&gt; Wireguard -&gt; Peer Generator
# You will be asked to enter some data for the new peer, enter the following: 
## '''Instance:''' &lt;code&gt;WG_Member&lt;/code&gt;   
## '''Endpoint:''' &lt;code&gt;wg-admin.cursedsilicon.net:42070&lt;/code&gt;
## '''Name:''' &lt;code&gt;member.''&lt;Nickname of the new member&gt;''&lt;/code&gt;
## '''Public Key:''' &lt;code&gt;''&lt;their Wireguard public key they've sent over&gt;''&lt;/code&gt;
## '''Private Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Address:''' ''&lt;code&gt;&lt;Next highest IP from 100.89.128.0/22, this is their tunnel IP and is auto-filled&gt;&lt;/code&gt;''
## '''Pre-Shared Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Allowed IPs:''' &lt;code&gt;''&lt;the same as Address&gt;'', ''&lt;their routed subnet, [[How to Get Connected#But wait, what even is their routed subnet?|see below]]&gt;''&lt;/code&gt;
## '''Keepalive interval:''' ''&lt;code&gt;&lt;blank&gt;&lt;/code&gt;''
## '''DNS Servers:''' &lt;code&gt;''&lt;default value&gt;''&lt;/code&gt;
# Hit the "Store and generate next" button
# Navigate to VPN -&gt; Wireguard -&gt; Instances
# Hit the "Apply" button
# Do either one of these steps, depending on if you can SSH into the GRETAP endpoint container:
## SSH into the CGHMN Proxmox Server and enter the command &lt;code&gt;pct enter 10403&lt;/code&gt;
## SSH directly into the GRETAP endpoint (formerly VXLAN endpoint) container with &lt;code&gt;ssh root@172.23.4.103&lt;/code&gt;
# From there, run the following command: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh &lt;member-tunnel-ip&gt; &lt;member-name&gt;&lt;/code&gt; where you replace &lt;code&gt;&lt;member-tunnel-ip&gt;&lt;/code&gt; with the IP tunnel address of the member as it was set above in the '''Address''' field, without the &lt;code&gt;/32&lt;/code&gt; CIDR subnet mask, and replace the &lt;code&gt;&lt;member-name&gt;&lt;/code&gt; with the same value you've entered above in the '''Name''' field. For example, like this: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh 100.89.128.6 member.snep.test&lt;/code&gt; This will create a GRETAP (and for legacy purposes, a VXLAN) interface and bring them up automagically. ''Ignore the fact it still says "VXLAN" everywhere, it does both.''
# Now you can send the member their Wireguard Tunnel IP and their routed subnet over and they can finish their client-side setup according to the mini-tutorial above.
# Rember to add the member and their tunnel and subnet IPs to the [[CGHMN-IP-Allocations|IP allocations page]] :)

==== But wait, what even ''is'' their routed subnet? ====
Each members routed subnet comes per default from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IPv4 block and has a &lt;code&gt;/24&lt;/code&gt; mask. This subnet is their "Retro LAN", to which all their retro computers are hooked into via the router of their choosing. By default, NAT is enabled on the routers, so it wouldn't make a difference which subnet is used on the remote end for the retro machines. However, if someone wants to host servers in the CGHMN and doesn't want to do port forwading, they can disable NAT and let other membres directly connect to their machines via this routed subnet.

To get the routed subnet of a member, take the number from the last octet of the Wireguard tunnel IP of a member, say &lt;code&gt;100.89.128.'''6'''&lt;/code&gt;, and put it into the third octet of the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IP block and replace the &lt;code&gt;/13&lt;/code&gt; with &lt;code&gt;/24&lt;/code&gt;, so you get &lt;code&gt;100.96.'''6'''.0/24&lt;/code&gt;. That is their routed subnet, simple as that!</text>
    <sha1>988f3b8f184e8df119a34a1093c6565696cfa5aa</sha1>
  </revision>
  <revision>
    <id>188</id>
    <parentid>173</parentid>
    <timestamp>2025-05-22T08:55:48Z</timestamp>
    <contributor>
      <username>Theothertom</username>
      <id>11</id>
    </contributor>
    <comment>Add a link to network status mailing list</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10819" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
This is a quick and dirty "how do I get on CGHMN" 

'''Since the service is in "closed beta" these steps are a bit vague and manual. But over time as we figure out what works we'll add more connection methods and better documentation'''

=== Step 1: ===
[[Signup|'''Let us know you'd like to connect!''']] 

(We'll need information from you such as your Wireguard Pubkey to let you connect to the network)[[File:CGHMN.png|thumb|319x319px|Example CGHMN Router Setup using a GL-AR300M and basic network switch]]

=== Hardware requirements ===
To connect your retro machine(s) to the CGHMN, you'll need the following:
*'''An Ethernet connection on your retro device(s) of choice, with a TCP/IP (v4) stack for now! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works.'''

* '''Something with the ability to run Wireguard and forward IPv4 packets at the minimum and, for any non-IP packets, &lt;code&gt;gretap&lt;/code&gt; and &lt;code&gt;nftables&lt;/code&gt;. Personally we recommend something running OpenWRT, like the [https://www.gl-inet.com/products/gl-ar300m GL-AR300M] which we have successfully tested to work. We're currently working on a pre-built image for some select routers to make the setup easier for new members. A script to configure already existing OpenWRT instances can be found below.'''
* Alternatively, you can also run the CGHMN routing on any standard Linux box which has at least one Ethernet port and either a second one or WiFi for internet connectivity. &lt;s&gt;A basic script to set up a Linux machine as a router is posted below&lt;/s&gt; (TODO!).

* '''Optionally: A simple network switch, in case you want to add multiple machines to the network. You plug one end into the CGHMN Router box and then your clients can all access CGHMN. Super easy!'''

On the right is an example of what a CGHMN router setup could look like.

=== Get connected - With OpenWRT ===
If you chose to go with an OpenWRT compatible router or want to run OpenWRT on typical x86 hardware/in a VM, you can follow these steps to get yourself connected to the CGHMN:

# Update your OpenWRT install to the latest version to ensure all required packages are available and compatible.
# Download [https://raw.githubusercontent.com/jonasluehrig/cghmn-get-connected/refs/heads/main/openwrt/setup-cghmn.sh this script from GitHub] to your OpenWRT router via SSH
# Run the following commands on the router:
## &lt;code&gt;ash setup-cghmn.sh install-pkgs&lt;/code&gt;
## &lt;code&gt;ash setup-cghmn.sh init&lt;/code&gt;
## You will be asked what network port you'd like to use for the Retro LAN. This is where you will plug in your retro machines to be part of the CGHMN. Choose a port that is not assigned to any OpenWRT interface like '''lan''' or '''wan''' or which not already part of a bridge and enter the Linux interface name, e.g. &lt;code&gt;eth1&lt;/code&gt;, then press &lt;code&gt;[Enter]&lt;/code&gt; to continue. If your router only has two ports and you're using one for WAN, then you first have to [https://openwrt.org/docs/guide-user/luci/luci.secure#allow_access_from_internet enable the web UI and SSH access via the '''wan''' OpenWRT interface], remove the entire '''lan''' OpenWRT interface to free the network port and continue the setup over the IP address your router got on its WAN side. If you only have a single Ethernet port, you're running on a router setup we can't really recommend, however you can configure VLANs and use a managed switch to both get a WAN DHCP address for internet access and have a separate VLAN for the Retro LAN bridge over a single port. This is commonly referred to as "[[wikipedia:Router_on_a_stick|router on a stick]]". Just enter the VLAN interface name here if you choose to go that route.
# Now you will be given some information on the console, including a Wireguard public key. Send one of the CGHMN admins (currently CursedSilicon and Snep) that key so we can add your router to our Wireguard server.
# In return, you will receive a tunnel IPv4 address (&lt;code&gt;100.89.128.x/32&lt;/code&gt;) and a routed IPv4 subnet (&lt;code&gt;100.96.x.0/24&lt;/code&gt;) from us. These will be needed on the third and final step of the setup script:
## &lt;code&gt;ash setup-cghmn.sh set-tunnel-ip&lt;/code&gt;
# Once the script completed successfully, reboot the router to ensure all interfaces are up properly. After the reboot, your retro devices should receive an IP address in your routed IPv4 subnet on the Retro LAN port you chose above and be able to communicate with other machines on the CGHMN network.

=== Get Connected - Manually (Linux, Wireguard only, GRETAP follows shortly) ===
In case you want to setup a connection into the network manually, here are the required steps and information you should be needing:

* Generate a Wireguard private key and public key, this command writes a fresh Wireguard private key to &lt;code&gt;private-key&lt;/code&gt; and the corresponsing public key to &lt;code&gt;public-key&lt;/code&gt;:

 $ wg genkey | tee private-key | wg pubkey &gt; public-key

* NEVER share your private key, even with us! It should never be required outside of your own Wireguard setup!
* You will, however, need to share your public key with us. Send CursedSilicon or Snep on the Discord or via IRC a message including the public key and we'll add you to the tunnel.
* In return, you'll get two IP addresses from us: Your tunnel IP address, with which your router talks to our router, and a routed subnet, from which you can assign IPs to your own machines so they can talk to other CGHMN member devices on the network without NAT in the way.
* Next, you'll need to fill a Wireguard configuration file with the two IP addresses, like below:

 [Interface]
 PrivateKey = &lt;Your private key goes here&gt;
 Address = &lt;Your tunnel IP address goes here&gt;/32
 DNS = 100.89.128.0
 MTU = 1420
 
 [Peer]
 PublicKey = k/QiJIbMakMKgTCHVt8/D+8k4DzRVM6U33F3gMZfRUg=
 Endpoint = wg-admin.cursedsilicon.net:42070
 AllowedIPs = 172.23.0.0/16, 100.89.128.0/22, 100.96.0.0/13
 PersistentKeepalive = 15

* Save this file as &lt;code&gt;wg-cghmn.conf&lt;/code&gt;, for example.
* Then, run &lt;code&gt;wg-quick up ./wg-cghmn.conf&lt;/code&gt;, perhaps requiring &lt;code&gt;doas&lt;/code&gt;/&lt;code&gt;sudo&lt;/code&gt;, to bring the tunnel up and connect to the network!

This should bring whatever system you've set the tunnel up on onto the network and is now reachable for other members on the network, as long as the firewall on your device is congfigured accordingly, of course.

&lt;nowiki&gt;#&lt;/nowiki&gt;TODO: Add example of routed subnet configuration, perhaps on a different Wiki site

=== Get connected - Server Side, the Admins Guide ===
[[File:Example Configuration for new Wireguard Peer on Core Router.png|thumb|Example Configuration for new Wireguard Peer on Core Router]]
To get a member onto the network, they will send an admin of the project their randomly generated Wireguard key during the setup via the OpenWRT script. Here are the steps that admin will have to follow to get them up and running on the server side:

# Log in on the [https://router.core.cghmn:8443 Core Router] over an existing CGHMN network link
# Navigate to VPN -&gt; Wireguard -&gt; Peer Generator
# You will be asked to enter some data for the new peer, enter the following: 
## '''Instance:''' &lt;code&gt;WG_Member&lt;/code&gt;   
## '''Endpoint:''' &lt;code&gt;wg-admin.cursedsilicon.net:42070&lt;/code&gt;
## '''Name:''' &lt;code&gt;member.''&lt;Nickname of the new member&gt;''&lt;/code&gt;
## '''Public Key:''' &lt;code&gt;''&lt;their Wireguard public key they've sent over&gt;''&lt;/code&gt;
## '''Private Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Address:''' ''&lt;code&gt;&lt;Next highest IP from 100.89.128.0/22, this is their tunnel IP and is auto-filled&gt;&lt;/code&gt;''
## '''Pre-Shared Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Allowed IPs:''' &lt;code&gt;''&lt;the same as Address&gt;'', ''&lt;their routed subnet, [[How to Get Connected#But wait, what even is their routed subnet?|see below]]&gt;''&lt;/code&gt;
## '''Keepalive interval:''' ''&lt;code&gt;&lt;blank&gt;&lt;/code&gt;''
## '''DNS Servers:''' &lt;code&gt;''&lt;default value&gt;''&lt;/code&gt;
# Hit the "Store and generate next" button
# Navigate to VPN -&gt; Wireguard -&gt; Instances
# Hit the "Apply" button
# Do either one of these steps, depending on if you can SSH into the GRETAP endpoint container:
## SSH into the CGHMN Proxmox Server and enter the command &lt;code&gt;pct enter 10403&lt;/code&gt;
## SSH directly into the GRETAP endpoint (formerly VXLAN endpoint) container with &lt;code&gt;ssh root@172.23.4.103&lt;/code&gt;
# From there, run the following command: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh &lt;member-tunnel-ip&gt; &lt;member-name&gt;&lt;/code&gt; where you replace &lt;code&gt;&lt;member-tunnel-ip&gt;&lt;/code&gt; with the IP tunnel address of the member as it was set above in the '''Address''' field, without the &lt;code&gt;/32&lt;/code&gt; CIDR subnet mask, and replace the &lt;code&gt;&lt;member-name&gt;&lt;/code&gt; with the same value you've entered above in the '''Name''' field. For example, like this: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh 100.89.128.6 member.snep.test&lt;/code&gt; This will create a GRETAP (and for legacy purposes, a VXLAN) interface and bring them up automagically. ''Ignore the fact it still says "VXLAN" everywhere, it does both.''
# Now you can send the member their Wireguard Tunnel IP and their routed subnet over and they can finish their client-side setup according to the mini-tutorial above.
# Rember to add the member and their tunnel and subnet IPs to the [[CGHMN-IP-Allocations|IP allocations page]] :)

==== But wait, what even ''is'' their routed subnet? ====
Each members routed subnet comes per default from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IPv4 block and has a &lt;code&gt;/24&lt;/code&gt; mask. This subnet is their "Retro LAN", to which all their retro computers are hooked into via the router of their choosing. By default, NAT is enabled on the routers, so it wouldn't make a difference which subnet is used on the remote end for the retro machines. However, if someone wants to host servers in the CGHMN and doesn't want to do port forwading, they can disable NAT and let other membres directly connect to their machines via this routed subnet.

To get the routed subnet of a member, take the number from the last octet of the Wireguard tunnel IP of a member, say &lt;code&gt;100.89.128.'''6'''&lt;/code&gt;, and put it into the third octet of the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IP block and replace the &lt;code&gt;/13&lt;/code&gt; with &lt;code&gt;/24&lt;/code&gt;, so you get &lt;code&gt;100.96.'''6'''.0/24&lt;/code&gt;. That is their routed subnet, simple as that!

=== After you get connected ===
There are a few optional things you might want to do.

==== Network mailing list ====
There is a mailing list you can subscribe to if you want to be notified about things that may affect CGHMN or core services. You can subscribe to the list here: https://berwick-upon-tweed.cobaltqu.be/postorius/lists/cghmn-announce.lists.cobaltqu.be/.


If you need to post to the list, you will need to subscribe before you can be added to the list of poster.</text>
    <sha1>9153f4f98da9bf93a423d140c3439008adabffbe</sha1>
  </revision>
  <revision>
    <id>193</id>
    <parentid>188</parentid>
    <timestamp>2025-05-26T02:47:51Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Minor readability change</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10843" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
This is a quick and dirty "how do I get on CGHMN" 

'''Since the service is in "closed beta" these steps are a bit vague and manual. But over time as we figure out what works we'll add more connection methods and better documentation'''

=== Step 1: ===
[[Signup|'''Let us know you'd like to connect!''']] 

(We'll need information from you such as your Wireguard Pubkey to let you connect to the network)[[File:CGHMN.png|thumb|319x319px|Example CGHMN Router Setup using a GL-AR300M and basic network switch]]

=== Hardware requirements ===
To connect your retro machine(s) to the CGHMN, you'll need the following:
*'''An Ethernet connection on your retro device(s) of choice, with a TCP/IP (v4) stack for now! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works.'''

* '''Something with the ability to run Wireguard and forward IPv4 packets at the minimum and, for any non-IP packets, &lt;code&gt;gretap&lt;/code&gt; and &lt;code&gt;nftables&lt;/code&gt;. Personally we recommend something running OpenWRT, like the [https://www.gl-inet.com/products/gl-ar300m GL-AR300M] which we have successfully tested to work. We're currently working on a pre-built image for some select routers to make the setup easier for new members. A script to configure already existing OpenWRT instances can be found below.'''
* Alternatively, you can also run the CGHMN routing on any standard Linux box which has at least one Ethernet port and either a second one or WiFi for internet connectivity. &lt;s&gt;A basic script to set up a Linux machine as a router is posted below&lt;/s&gt; (TODO!).

* '''Optionally: A simple network switch, in case you want to add multiple machines to the network. You plug one end into the CGHMN Router box and then your clients can all access CGHMN. Super easy!'''

On the right is an example of what a CGHMN router setup could look like.

=== Get connected - With OpenWRT ===
If you chose to go with an OpenWRT compatible router or want to run OpenWRT on typical x86 hardware/in a VM, you can follow these steps to get yourself connected to the CGHMN:

# Update your OpenWRT install to the latest version to ensure all required packages are available and compatible.
# Download [https://raw.githubusercontent.com/jonasluehrig/cghmn-get-connected/refs/heads/main/openwrt/setup-cghmn.sh this script from GitHub] to your OpenWRT router via SSH
# Run the following commands on the router:
## &lt;code&gt;ash setup-cghmn.sh install-pkgs&lt;/code&gt;
## &lt;code&gt;ash setup-cghmn.sh init&lt;/code&gt;
## You will be asked what network port you'd like to use for the Retro LAN. This is where you will plug in your retro machines to be part of the CGHMN. Choose a port that is not assigned to any OpenWRT interface like '''lan''' or '''wan''' or which not already part of a bridge and enter the Linux interface name, e.g. &lt;code&gt;eth1&lt;/code&gt;, then press &lt;code&gt;[Enter]&lt;/code&gt; to continue. If your router only has two ports and you're using one for WAN, then you first have to [https://openwrt.org/docs/guide-user/luci/luci.secure#allow_access_from_internet enable the web UI and SSH access via the '''wan''' OpenWRT interface], remove the entire '''lan''' OpenWRT interface to free the network port and continue the setup over the IP address your router got on its WAN side. If you only have a single Ethernet port, you're running on a router setup we can't really recommend, however you can configure VLANs and use a managed switch to both get a WAN DHCP address for internet access and have a separate VLAN for the Retro LAN bridge over a single port. This is commonly referred to as "[[wikipedia:Router_on_a_stick|router on a stick]]". Just enter the VLAN interface name here if you choose to go that route.
# Now you will be given some information on the console, including a Wireguard public key. Send one of the CGHMN admins (currently CursedSilicon and Snep) that key so we can add your router to our Wireguard server.
# In return, you will receive a tunnel IPv4 address (&lt;code&gt;100.89.128.x/32&lt;/code&gt;) and a routed IPv4 subnet (&lt;code&gt;100.96.x.0/24&lt;/code&gt;) from us. These will be needed on the third and final step of the setup script:
## &lt;code&gt;ash setup-cghmn.sh set-tunnel-ip&lt;/code&gt;
# Once the script completed successfully, reboot the router to ensure all interfaces are up properly. After the reboot, your retro devices should receive an IP address in your routed IPv4 subnet on the Retro LAN port you chose above and be able to communicate with other machines on the CGHMN network.

=== Get Connected - Manually (Linux, Wireguard only, GRETAP follows shortly) ===
In case you want to setup a connection into the network manually, here are the required steps and information you should be needing:

* Generate a Wireguard private key and public key, this command writes a fresh Wireguard private key to &lt;code&gt;private-key&lt;/code&gt; and the corresponsing public key to &lt;code&gt;public-key&lt;/code&gt;:

 $ wg genkey | tee private-key | wg pubkey &gt; public-key

* NEVER share your private key, even with us! It should never be required outside of your own Wireguard setup!
* You will, however, need to share your public key with us. Send CursedSilicon or Snep on the Discord or via IRC a message including the public key and we'll add you to the tunnel.
* In return, you'll get two IP addresses from us: Your tunnel IP address, with which your router talks to our router, and a routed subnet, from which you can assign IPs to your own machines so they can talk to other CGHMN member devices on the network without NAT in the way.
* Next, you'll need to fill a Wireguard configuration file with the two IP addresses, like below:

 [Interface]
 PrivateKey = &lt;Your private key goes here&gt;
 Address = &lt;Your tunnel IP address goes here&gt;/32
 DNS = 100.89.128.0
 MTU = 1420
 
 [Peer]
 PublicKey = k/QiJIbMakMKgTCHVt8/D+8k4DzRVM6U33F3gMZfRUg=
 Endpoint = wg-admin.cursedsilicon.net:42070
 AllowedIPs = 172.23.0.0/16, 100.89.128.0/22, 100.96.0.0/13
 PersistentKeepalive = 15

* Save this file as &lt;code&gt;wg-cghmn.conf&lt;/code&gt;, for example.
* Then, run &lt;code&gt;wg-quick up ./wg-cghmn.conf&lt;/code&gt;, perhaps requiring &lt;code&gt;doas&lt;/code&gt;/&lt;code&gt;sudo&lt;/code&gt;, to bring the tunnel up and connect to the network!

This should bring whatever system you've set the tunnel up on onto the network and is now reachable for other members on the network, as long as the firewall on your device is congfigured accordingly, of course.

&lt;nowiki&gt;#&lt;/nowiki&gt;TODO: Add example of routed subnet configuration, perhaps on a different Wiki site

=== Get connected - Server Side, the Admins Guide ===
[[File:Example Configuration for new Wireguard Peer on Core Router.png|thumb|Example Configuration for new Wireguard Peer on Core Router]]
To get a member onto the network, they will send an admin of the project their randomly generated Wireguard key during the setup via the OpenWRT script. Here are the steps that admin will have to follow to get them up and running on the server side:

# Log in on the [https://router.core.cghmn:8443 Core Router] over an existing CGHMN network link
# Navigate to VPN -&gt; Wireguard -&gt; Peer Generator
# You will be asked to enter some data for the new peer, enter the following: 
## '''Instance:''' &lt;code&gt;WG_Member&lt;/code&gt;   
## '''Endpoint:''' &lt;code&gt;wg-admin.cursedsilicon.net:42070&lt;/code&gt;
## '''Name:''' &lt;code&gt;member.''&lt;Nickname of the new member&gt;''&lt;/code&gt;
## '''Public Key:''' &lt;code&gt;''&lt;their Wireguard public key they've sent over&gt;''&lt;/code&gt;
## '''Private Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Address:''' ''&lt;code&gt;&lt;Next highest IP from 100.89.128.0/22, this is their tunnel IP and is auto-filled&gt;&lt;/code&gt;''
## '''Pre-Shared Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Allowed IPs:''' &lt;code&gt;''&lt;the same as Address&gt;'', ''&lt;their routed subnet, [[How to Get Connected#But wait, what even is their routed subnet?|see below]]&gt;''&lt;/code&gt;
## '''Keepalive interval:''' ''&lt;code&gt;&lt;blank&gt;&lt;/code&gt;''
## '''DNS Servers:''' &lt;code&gt;''&lt;default value&gt;''&lt;/code&gt;
# Hit the "Store and generate next" button
# Navigate to VPN -&gt; Wireguard -&gt; Instances
# Hit the "Apply" button
# Do '''either one''' '''(not both!)''' of these steps, depending on if you can SSH into the GRETAP endpoint container:
## SSH into the CGHMN Proxmox Server and enter the command &lt;code&gt;pct enter 10403&lt;/code&gt;
## SSH directly into the GRETAP endpoint (formerly VXLAN endpoint) container with &lt;code&gt;ssh root@172.23.4.103&lt;/code&gt;
# From there, run the following command: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh &lt;member-tunnel-ip&gt; &lt;member-name&gt;&lt;/code&gt; where you replace &lt;code&gt;&lt;member-tunnel-ip&gt;&lt;/code&gt; with the IP tunnel address of the member as it was set above in the '''Address''' field, without the &lt;code&gt;/32&lt;/code&gt; CIDR subnet mask, and replace the &lt;code&gt;&lt;member-name&gt;&lt;/code&gt; with the same value you've entered above in the '''Name''' field. For example, like this: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh 100.89.128.6 member.snep.test&lt;/code&gt; This will create a GRETAP (and for legacy purposes, a VXLAN) interface and bring them up automagically. ''Ignore the fact it still says "VXLAN" everywhere, it does both.''
# Now you can send the member their Wireguard Tunnel IP and their routed subnet over and they can finish their client-side setup according to the mini-tutorial above.
# Rember to add the member and their tunnel and subnet IPs to the [[CGHMN-IP-Allocations|IP allocations page]] :)

==== But wait, what even ''is'' their routed subnet? ====
Each members routed subnet comes per default from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IPv4 block and has a &lt;code&gt;/24&lt;/code&gt; mask. This subnet is their "Retro LAN", to which all their retro computers are hooked into via the router of their choosing. By default, NAT is enabled on the routers, so it wouldn't make a difference which subnet is used on the remote end for the retro machines. However, if someone wants to host servers in the CGHMN and doesn't want to do port forwading, they can disable NAT and let other membres directly connect to their machines via this routed subnet.

To get the routed subnet of a member, take the number from the last octet of the Wireguard tunnel IP of a member, say &lt;code&gt;100.89.128.'''6'''&lt;/code&gt;, and put it into the third octet of the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IP block and replace the &lt;code&gt;/13&lt;/code&gt; with &lt;code&gt;/24&lt;/code&gt;, so you get &lt;code&gt;100.96.'''6'''.0/24&lt;/code&gt;. That is their routed subnet, simple as that!

=== After you get connected ===
There are a few optional things you might want to do.

==== Network mailing list ====
There is a mailing list you can subscribe to if you want to be notified about things that may affect CGHMN or core services. You can subscribe to the list here: https://berwick-upon-tweed.cobaltqu.be/postorius/lists/cghmn-announce.lists.cobaltqu.be/.


If you need to post to the list, you will need to subscribe before you can be added to the list of poster.</text>
    <sha1>de6a5612a135398df2e9f9142f771ca3c8399c77</sha1>
  </revision>
  <revision>
    <id>194</id>
    <parentid>193</parentid>
    <timestamp>2025-05-26T13:38:25Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>Slight updates to the setup script</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11170" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
This is a quick and dirty "how do I get on CGHMN" 

'''Since the service is in "closed beta" these steps are a bit vague and manual. But over time as we figure out what works we'll add more connection methods and better documentation'''

=== Step 1: ===
[[Signup|'''Let us know you'd like to connect!''']] 

(We'll need information from you such as your Wireguard Pubkey to let you connect to the network)[[File:CGHMN.png|thumb|319x319px|Example CGHMN Router Setup using a GL-AR300M and basic network switch]]

=== Hardware requirements ===
To connect your retro machine(s) to the CGHMN, you'll need the following:
*'''An Ethernet connection on your retro device(s) of choice, with a TCP/IP (v4) stack for now! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works.'''

* '''Something with the ability to run Wireguard and forward IPv4 packets at the minimum and, for any non-IP packets, &lt;code&gt;gretap&lt;/code&gt; and &lt;code&gt;nftables&lt;/code&gt;. Personally we recommend something running OpenWRT, like the [https://www.gl-inet.com/products/gl-ar300m GL-AR300M] which we have successfully tested to work. We're currently working on a pre-built image for some select routers to make the setup easier for new members. A script to configure already existing OpenWRT instances can be found below.'''
* Alternatively, you can also run the CGHMN routing on any standard Linux box which has at least one Ethernet port and either a second one or WiFi for internet connectivity. &lt;s&gt;A basic script to set up a Linux machine as a router is posted below&lt;/s&gt; (TODO!).

* '''Optionally: A simple network switch, in case you want to add multiple machines to the network. You plug one end into the CGHMN Router box and then your clients can all access CGHMN. Super easy!'''

On the right is an example of what a CGHMN router setup could look like.

=== Get connected - With OpenWRT ===
If you chose to go with an OpenWRT compatible router or want to run OpenWRT on typical x86 hardware/in a VM, you can follow these steps to get yourself connected to the CGHMN:

# Update your OpenWRT install to the latest version to ensure all required packages are available and compatible.
# Download [https://raw.githubusercontent.com/jonasluehrig/cghmn-get-connected/refs/heads/main/openwrt/setup-cghmn.sh this script from GitHub] to your OpenWRT router: &lt;code&gt;wget https://cghmn.snep.zip/connect.sh&lt;/code&gt;
# Run the following commands on the router:
## &lt;code&gt;ash setup-cghmn.sh install-pkgs&lt;/code&gt;
## &lt;code&gt;ash setup-cghmn.sh init&lt;/code&gt;
## You will be asked what network port you'd like to use for the Retro LAN. This is where you will plug in your retro machines to be part of the CGHMN. Choose a port that is not assigned to any OpenWRT interface like '''lan''' or '''wan''' or which not already part of a bridge and enter the Linux interface name, e.g. &lt;code&gt;eth1&lt;/code&gt;, then press &lt;code&gt;[Enter]&lt;/code&gt; to continue. If your router only has two ports and you're using one for WAN, then you first have to [https://openwrt.org/docs/guide-user/luci/luci.secure#allow_access_from_internet enable the web UI and SSH access via the '''wan''' OpenWRT interface], remove the entire '''lan''' OpenWRT interface to free the network port and continue the setup over the IP address your router got on its WAN side. If you only have a single Ethernet port, you're running on a router setup we can't really recommend, however you can configure VLANs and use a managed switch to both get a WAN DHCP address for internet access and have a separate VLAN for the Retro LAN bridge over a single port. This is commonly referred to as "[[wikipedia:Router_on_a_stick|router on a stick]]". Just enter the VLAN interface name here if you choose to go that route.
# Now you will be given some information on the console, including a Wireguard public key. Send one of the CGHMN admins (currently CursedSilicon and Snep) that key so we can add your router to our Wireguard server. If you cannot copy-paste, for example, because you're on a VM VNC console, you can run &lt;code&gt;ash setup-cghmn.sh pubkey-qr&lt;/code&gt; to get a QR code printout of your public key, which can be scanned with a phone, tablet or software QR code parser to get the key as copy-pastable text.
# In return, you will receive a tunnel IPv4 address (&lt;code&gt;100.89.128.x/32&lt;/code&gt;) and a routed IPv4 subnet (&lt;code&gt;100.96.x.0/24&lt;/code&gt;) from us. These will be needed on the third and final step of the setup script:
## &lt;code&gt;ash setup-cghmn.sh set-tunnel-ip&lt;/code&gt;
# Once the script completed successfully, reboot the router to ensure all interfaces are up properly. After the reboot, your retro devices should receive an IP address in your routed IPv4 subnet on the Retro LAN port you chose above and be able to communicate with other machines on the CGHMN network.

=== Get Connected - Manually (Linux, Wireguard only, GRETAP follows shortly) ===
In case you want to setup a connection into the network manually, here are the required steps and information you should be needing:

* Generate a Wireguard private key and public key, this command writes a fresh Wireguard private key to &lt;code&gt;private-key&lt;/code&gt; and the corresponsing public key to &lt;code&gt;public-key&lt;/code&gt;:

 $ wg genkey | tee private-key | wg pubkey &gt; public-key

* NEVER share your private key, even with us! It should never be required outside of your own Wireguard setup!
* You will, however, need to share your public key with us. Send CursedSilicon or Snep on the Discord or via IRC a message including the public key and we'll add you to the tunnel.
* In return, you'll get two IP addresses from us: Your tunnel IP address, with which your router talks to our router, and a routed subnet, from which you can assign IPs to your own machines so they can talk to other CGHMN member devices on the network without NAT in the way.
* Next, you'll need to fill a Wireguard configuration file with the two IP addresses, like below:

 [Interface]
 PrivateKey = &lt;Your private key goes here&gt;
 Address = &lt;Your tunnel IP address goes here&gt;/32
 DNS = 100.89.128.0
 MTU = 1420
 
 [Peer]
 PublicKey = k/QiJIbMakMKgTCHVt8/D+8k4DzRVM6U33F3gMZfRUg=
 Endpoint = wg-admin.cursedsilicon.net:42070
 AllowedIPs = 172.23.0.0/16, 100.89.128.0/22, 100.96.0.0/13
 PersistentKeepalive = 15

* Save this file as &lt;code&gt;wg-cghmn.conf&lt;/code&gt;, for example.
* Then, run &lt;code&gt;wg-quick up ./wg-cghmn.conf&lt;/code&gt;, perhaps requiring &lt;code&gt;doas&lt;/code&gt;/&lt;code&gt;sudo&lt;/code&gt;, to bring the tunnel up and connect to the network!

This should bring whatever system you've set the tunnel up on onto the network and is now reachable for other members on the network, as long as the firewall on your device is congfigured accordingly, of course.

&lt;nowiki&gt;#&lt;/nowiki&gt;TODO: Add example of routed subnet configuration, perhaps on a different Wiki site

=== Get connected - Server Side, the Admins Guide ===
[[File:Example Configuration for new Wireguard Peer on Core Router.png|thumb|Example Configuration for new Wireguard Peer on Core Router]]
To get a member onto the network, they will send an admin of the project their randomly generated Wireguard key during the setup via the OpenWRT script. Here are the steps that admin will have to follow to get them up and running on the server side:

# Log in on the [https://router.core.cghmn:8443 Core Router] over an existing CGHMN network link
# Navigate to VPN -&gt; Wireguard -&gt; Peer Generator
# You will be asked to enter some data for the new peer, enter the following: 
## '''Instance:''' &lt;code&gt;WG_Member&lt;/code&gt;   
## '''Endpoint:''' &lt;code&gt;wg-admin.cursedsilicon.net:42070&lt;/code&gt;
## '''Name:''' &lt;code&gt;member.''&lt;Nickname of the new member&gt;''&lt;/code&gt;
## '''Public Key:''' &lt;code&gt;''&lt;their Wireguard public key they've sent over&gt;''&lt;/code&gt;
## '''Private Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Address:''' ''&lt;code&gt;&lt;Next highest IP from 100.89.128.0/22, this is their tunnel IP and is auto-filled&gt;&lt;/code&gt;''
## '''Pre-Shared Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Allowed IPs:''' &lt;code&gt;''&lt;the same as Address&gt;'', ''&lt;their routed subnet, [[How to Get Connected#But wait, what even is their routed subnet?|see below]]&gt;''&lt;/code&gt;
## '''Keepalive interval:''' ''&lt;code&gt;&lt;blank&gt;&lt;/code&gt;''
## '''DNS Servers:''' &lt;code&gt;''&lt;default value&gt;''&lt;/code&gt;
# Hit the "Store and generate next" button
# Navigate to VPN -&gt; Wireguard -&gt; Instances
# Hit the "Apply" button
# Do '''either one''' '''(not both!)''' of these steps, depending on if you can SSH into the GRETAP endpoint container:
## SSH into the CGHMN Proxmox Server and enter the command &lt;code&gt;pct enter 10403&lt;/code&gt;
## SSH directly into the GRETAP endpoint (formerly VXLAN endpoint) container with &lt;code&gt;ssh root@172.23.4.103&lt;/code&gt;
# From there, run the following command: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh &lt;member-tunnel-ip&gt; &lt;member-name&gt;&lt;/code&gt; where you replace &lt;code&gt;&lt;member-tunnel-ip&gt;&lt;/code&gt; with the IP tunnel address of the member as it was set above in the '''Address''' field, without the &lt;code&gt;/32&lt;/code&gt; CIDR subnet mask, and replace the &lt;code&gt;&lt;member-name&gt;&lt;/code&gt; with the same value you've entered above in the '''Name''' field. For example, like this: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh 100.89.128.6 member.snep.test&lt;/code&gt; This will create a GRETAP (and for legacy purposes, a VXLAN) interface and bring them up automagically. ''Ignore the fact it still says "VXLAN" everywhere, it does both.''
# Now you can send the member their Wireguard Tunnel IP and their routed subnet over and they can finish their client-side setup according to the mini-tutorial above.
# Rember to add the member and their tunnel and subnet IPs to the [[CGHMN-IP-Allocations|IP allocations page]] :)

==== But wait, what even ''is'' their routed subnet? ====
Each members routed subnet comes per default from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IPv4 block and has a &lt;code&gt;/24&lt;/code&gt; mask. This subnet is their "Retro LAN", to which all their retro computers are hooked into via the router of their choosing. By default, NAT is enabled on the routers, so it wouldn't make a difference which subnet is used on the remote end for the retro machines. However, if someone wants to host servers in the CGHMN and doesn't want to do port forwading, they can disable NAT and let other membres directly connect to their machines via this routed subnet.

To get the routed subnet of a member, take the number from the last octet of the Wireguard tunnel IP of a member, say &lt;code&gt;100.89.128.'''6'''&lt;/code&gt;, and put it into the third octet of the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IP block and replace the &lt;code&gt;/13&lt;/code&gt; with &lt;code&gt;/24&lt;/code&gt;, so you get &lt;code&gt;100.96.'''6'''.0/24&lt;/code&gt;. That is their routed subnet, simple as that!

=== After you get connected ===
There are a few optional things you might want to do.

==== Network mailing list ====
There is a mailing list you can subscribe to if you want to be notified about things that may affect CGHMN or core services. You can subscribe to the list here: https://berwick-upon-tweed.cobaltqu.be/postorius/lists/cghmn-announce.lists.cobaltqu.be/.


If you need to post to the list, you will need to subscribe before you can be added to the list of poster.</text>
    <sha1>e469b096511cbadb740a649a398bb3cad38c7bbb</sha1>
  </revision>
</page>
<page arvcontinue="20250506224236|158">
  <title>Category:Compu-Global-Hyper-Mega-Net</title>
  <ns>14</ns>
  <id>85</id>
  <revision>
    <id>166</id>
    <timestamp>2025-05-11T02:31:14Z</timestamp>
    <contributor>
      <username>Ilostmybagel</username>
      <id>3</id>
    </contributor>
    <comment>Created page with "Pages relating to the Compu-Global-Hyper-Mega-Net"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="49" xml:space="preserve">Pages relating to the Compu-Global-Hyper-Mega-Net</text>
    <sha1>3f46513c5c4d58f0a215eda980400b20e5bb5b88</sha1>
  </revision>
</page>
<page arvcontinue="20250506224236|158">
  <title>Compu-Global-Hyper-Mega-Net</title>
  <ns>0</ns>
  <id>61</id>
  <revision>
    <id>167</id>
    <parentid>138</parentid>
    <timestamp>2025-05-11T02:32:20Z</timestamp>
    <contributor>
      <username>Ilostmybagel</username>
      <id>3</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4254" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
=== Preamble ===
Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in its embryonic stages as I step through the trial-by-fire of the reality of setting up 1990's era telecommunications infrastructure in a way that is both functional and not inconvenient for myself or others in the space it is physically housed in.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "fun" for us!


A longer term goal includes providing democratized access for users to begin submitting their own projects and content ala [[wikipedia:GeoCities|Geocities]] and setting up federated networking with other retro computing users, similar to GlobalTalk but with a larger scope of features and functionality
=== So what's this all about? ===


CGHMN is a collaborative project aimed to create a late 1990's/early 2000's compatible "internet" for retro computing enthusiasts and their machines

=== Okay so how do I connect to it ===


You can sign up '''[[Signup|right now]]!''' to "alpha test" the network

===  How fast is it? ===


Total internal network capacity is '''''1Gbps''''' (symmetric) due to limitations of the switches in operation. This speed may be raised or lowered depending on future federation with other members. 

Your speed will depend on factors such as how fast your device can run Wireguard and your internet connection 

=== Is this safe to use? I thought connecting old PC's to the internet was a bad idea! ===


Compu-Global-Hyper-Mega-Net is not accessible by the wider internet and is specifically designed to be a ''hermetically sealed'' network. Users can only connect via the above methods '''and can only communicate with other devices on the network'''. Users that violate the Terms of Service or attempt to abuse the network (or other members) will have their access '''permanently removed'''. With that said the usual rules about not downloading suspicious files and other "internet hygiene" rules still apply. While we don't expect bad actors to be a problem, please ensure that any files contributed to the network are scanned for malware first! [https://www.virustotal.com/gui/home/upload VirusTotal] provides free scanning services for this.

=== How can I help? ===


A lot of folks have offered to donate server hosting which is wonderful. Though not (yet!) required. The two biggest things we need are 


'''Donations to buy infrastructure''' (Particularly hard disks!) there's an Amazon Wishlist here that will get updated over time. https://www.amazon.com/hz/wishlist/ls/1W3S0E9IN7ZB7?ref_=wl_share


'''Volunteers who want to set up services'''. Want to come build a website? Run an old game server? Have some weird retro hardware you want to attach to the network? Please, reach out!</text>
    <sha1>f92df26e58e51d2f2d420dcc60b2630617ab9917</sha1>
  </revision>
</page>
<page arvcontinue="20250506224236|158">
  <title>CGHMN-Demo-Network</title>
  <ns>0</ns>
  <id>76</id>
  <revision>
    <id>168</id>
    <parentid>131</parentid>
    <timestamp>2025-05-11T02:33:01Z</timestamp>
    <contributor>
      <username>Ilostmybagel</username>
      <id>3</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19464" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
=== Demo Network for the Interim Computer Festival ===
This page documents the quickly set up demo network to show off the CGHMN network at the [https://sdf.org/icf/ SDF's Interim Computer Festival] taking place between March 22nd and 23rd. Consider this a sort-of draft, an experimental first version, a test on what might work and what doesn't.

Currently, the basics are up and running on the CGHMN Proxmox hypervisor living in the [https://devhack.net/ /dev/hack Hackerspace] in Seattle. These include a router and Wireguard endpoint through an OPNsense VM, a VXLAN tunnel endpoint container with some custom scripts to make deploying new member tunnel easier and two containers running a basic authoritative BIND DNS server for &lt;code&gt;.cghmn&lt;/code&gt; and &lt;code&gt;.retro&lt;/code&gt; and one hosting a custom, internal Certificate Authority for those domains.

=== Changes to the network layout ===
Since this page was written, there have been quite a lot of discussions about how and what we might change going forward, after the initial test of the network at the ICF was a success. The biggest change, so far, has been the idea to move away from VXLANs to GRETAP tunnels for the Layer 2 and non-IP Layer 3 traffic. This is mostly due to the fact that VXLANs, by their RFC definition, MAY NOT fragment packets coming into the VTEP (aka. a VXLAN tunnel endpoint) and packets flowing out of a VTEP MAY be reassembled if fragmented, but don't necessarily have to. In addition to this, the IP packets generated by the VXLAN tunnels have the Don't Fragment bit set, so those packets may also not be fragmented. This means that the underlying transport of the VXLAN tunnels, here Wireguard, would have to open a path that allows 1500 byte frames through its tunnel, which would make the tunnel packets themselves quite large at ~1600 bytes, which would then be fragmented by whatever routers are in between the client router and the CGHMN router. Turns out, that's quite inefficient. 

GRETAP tunnels, on the other hand, have the two flags &lt;code&gt;ignore-df&lt;/code&gt; and &lt;code&gt;nopmtudisc&lt;/code&gt;, which together with &lt;code&gt;ttl 255&lt;/code&gt; create a tunnel over IP, which can carry ''and fragment'' 1500 byte Ethernet frames over a smaller underlying transport, still Wireguard in this case. This was a massive boost not only in speed under certain circumstances, like running this all on a small travel router with a weak MIPS CPU, but also reliability, as less dropped packets could be observed and MTU blackholes finally not happening in our testing.

To bring up a GRETAP tunnel within the network to the CGHMN central router, use the following commands on a Linux box:&lt;blockquote&gt;&lt;code&gt;ip link add gretap-cghmn type gretap remote 172.23.4.103 dev wg0 ignore-df nopmtudisc ttl 255&lt;/code&gt;

&lt;code&gt;ip link set gretap-cghmn master br0 mtu 1500&lt;/code&gt;

&lt;code&gt;ip link set gretap-cghmn up&lt;/code&gt;&lt;/blockquote&gt;Where &lt;code&gt;wg0&lt;/code&gt; is your CGHMN Wireguard tunnel and &lt;code&gt;br0&lt;/code&gt; is the bridge you'd want to bridge the GRETAP tunnel to.

However, to improve performance more and make the network a little more reliable, there was another idea for a change: Sending routable IP traffic not over the Layher 2 tunnel, but rather routing it directly through the Wireguard tunnel, which already is a straight Layer 3 path to the CGHMN core router. This is possible due to the nftables &lt;code&gt;bridge&lt;/code&gt; filter table, which can match and filter packets on bridge interfaces, incuding what "bridge port" they come in and go out of. This means we can filter IP traffic from leaving the retro LAN bridge, to which you'd connect your retro machines via a phyiscal LAN port, by creating a filter that says "Block all traffic on bridge &lt;code&gt;br-retrolan&lt;/code&gt; which leaves through a GRETAP interface" and "Block all traffic on bridge &lt;code&gt;br-retrolan&lt;/code&gt; which comes in on a GRETAP interface". Now, you can assign the router a static IP address on the bridge, so it can talk to your retro machines, enable DHCP and NAT and route IP traffic from your machines straight to the CGHMN via Wireguard. In the future, this shall be extended to work without NAT on the client side, so that every member has a small subnet, /24 for example, which is routed to the Wireugard tunnel client IP. This also means that the VLAN1 described in the next section might not need an IP address in the future so that the VLAN1 is purely non-IP traffic at least from the CGHMN side of things.

Yet another idea mentioned was the ability to span tunnels directly between members, even without going through the CGHMN core network in the first place. This can be accomplished by creating another GRETAP interface whose &lt;code&gt;remote&lt;/code&gt; IP argument points to the IP of another members router, either through the existing CGHMN Wireguard tunnel or through a separate tunnel that you span between you and the other member. This GRETAP interface is then bridged to the &lt;code&gt;br-retrolan&lt;/code&gt; bridge and with a couple of (perhaps default) bridge firewall rules, you and the other member should be able to communicate directly! Of course, this also means we'd have to implement some sort of loopback protection not just on the member router side (the default bridge firewall rules mentioned in the last sentence), but also on the core router side. so this idea is not yet fully implemented for testing.

IP Allocations within the network are now kept track of [[CGHMN-IP-Allocations|in this Wiki page]], though the IPs listed there might not be applied in the current configuration yet.


=== Network Layout ===
This section describes the network layout currently set up for the CGHMN demo network, none of which is necessarily permanent and already set in stone. I (Snep) made some assumptions about domain names, IP addresses, firewall rules and general design ideas to get something up and running for the computer festival based on info from the many chats and discussions on the Cursed Silicon Discord's CGHMN channel (See [[Signup]] for more details). So, please feel free to give input on things you'd like to see changed or added!

On the Proxmox host, all VLANs mentioned below are available tagged on the bridge &lt;code&gt;brcghmn&lt;/code&gt;, with exception of VLAN1, which is untagged and the default network when a new container or VM is added to this bridge.

For servers and retro clients, the subnet &lt;code&gt;172.23.0.0/16&lt;/code&gt; is currently in place, divided into smaller subnets, and might be subject to change later down the line. For Wireguard clients, the &lt;code&gt;100.89.128.0/22&lt;/code&gt; subnet out of the CGNAT block is used and again, might change later.

Below is a further breakdown of VLANs existing in this CGHMN demo network:

==== VLAN 1 - The Global LAN (172.23.0.0/22) ====
This network is our layer 2 bridged network to all members who wish to participate and is intended to be used for retro computers to directly communicate with each other even across the globe. This is accomplished by spanning a VXLAN tunnel across a Wireguard connection from the CGHMN server infrastructure to each members' router endpoint, which can be any OpenWRT compatible device that contains the packages for VXLANs and Wireguard. The idea is to bridge on of at least two available interfaces from said router to the VXLAN network and thus directly bridge any connected retro machines to VLAN1. All members will be in the same L2 broadcast domain, meaning even non-IP protocols that are able to run over Ethernet should be able to communicate with each other from all over the world.

Machines on this network are able to connect to all hosts on the Server VLAN (see below), the firewall for DNS, NTP and ICMP queries and to the root DNS and CA servers for DNS queries and HTTP access to the CA web server. They may also query DNS lookups at the legacy DNS server at &lt;code&gt;172.23.0.104&lt;/code&gt;. They are not, however, able to communicate with any hosts on the internet, the /dev/hack network or any of the other existing VLANs aside from specific exceptions.

Addresses are handed out via DHCP by the router in the range &lt;code&gt;172.23.1.1-172.23.3.254&lt;/code&gt;, the range &lt;code&gt;172.23.1.11-172.23.1.255&lt;/code&gt; is reserved for static hosts. The search domain for this network is &lt;code&gt;clients.retro&lt;/code&gt;.

==== VLAN 4 - Core Services (172.23.4.0/22) ====
This VLAN in intended for core internal services, like the root DNS server, VXLAN endpoint and our custom Certificate Authority. The Proxmox host also has an IP address in this subnet (&lt;code&gt;172.23.4.11&lt;/code&gt;), it does not however have any routes to the rest of this CGHMN demo infrastructure and thus can only be accessed from clients in the Core Services subnet. 

Hosts in this subnet may currently access the internet, the router for DNS, NTP and ICMP queries, query DNS lookups at the legacy DNS server at &lt;code&gt;172.23.4.104&lt;/code&gt; and the VXLAN endpoint may send UDP datagrams to anyone at port &lt;code&gt;4789&lt;/code&gt; for VXLAN tunnel replies, any other internal connections are prohibited.

Addresses are handed out via DHCP by the router in the range &lt;code&gt;172.23.7.1-172.23.7.254&lt;/code&gt;, the range &lt;code&gt;172.23.4.11-172.23.6.255&lt;/code&gt; is reserved for static hosts. The search domain for this network is &lt;code&gt;core.cghmn&lt;/code&gt;.

==== VLAN 8 - Servers (172.23.8.0/22) ====
This VLAN will contain all servers hosted and managed by members, which can be any (retro) service that works across an IP router. For anything that requires direct layer 2 access or the same broadcast domain as the client machines, it is advised to host said server in the Global LAN network. This is the only VLAN clients from the bridged Global LAN network may access freely, so members should be wary about what ports they open up for anyone outside of localhost. Another option is to run a tiny router instance based on OpenWRT in front of your server which will act as a basic firewall and NAT router behind which one can run their servers.

Hosts in this subnet may not access the internet inherently, however a firewall rule is in place that allows specific servers internet access, it is still uncertain if this will make it to the final CGHMN or if this subnet is also supposed to be entirely sealed off from the public internet. During a few chats on the Discord server, the idea of hosting local package mirrors of popular distros and projects was mentioned so that both modern and retro systems won't need to connect to internet servers for package installations and upgrades. Hosts may access the router for DNS, NTP and ICMP queries and query DNS lookups at the legacy DNS server at &lt;code&gt;172.23.4.104&lt;/code&gt;, other internal connections are prohibited.

Addresses are handed out via DHCP by the router in the range &lt;code&gt;172.23.11.1-172.23.11.254&lt;/code&gt;, the range &lt;code&gt;172.23.8.11-172.23.10.255&lt;/code&gt; is reserved for static hosts. The search domain for this network is &lt;code&gt;hosting.retro&lt;/code&gt;.

==== VLAN 12 - DMZ (172.23.12.0/22) ====
Currently not in use.


=== Containers and VMs ===
Containers and VMs on the Proxmox host are currently assigned in the 10000 ID range to keep clear of existing VMs.

There is one VM and three containers at the time of writing this:

==== VM 10001 (demo-chhmn-router) ====
This is the OPNsense VM running as the primary router, firewall, DHCP server and Wireguard endpoint for the demo network. Its login credentials are currently in the paws of Snep, as I'm still unsure where any passwords for the CGHMN are going to be stored safely and with proper access rights.

The router has the first IP in any of the available demo network subnets and responds to IPv4 and IPv4 ICMP packets, DNS queries to its local Unbound resolver and NTP sync requests to the built-in NTP server.

Unbound currently resolves all requests it cannot resolve locally recursively against the internet root servers and returns those replies to clients, this may be subject to change as we potentially plan on sealing the network off more. It is configured to forward all requests with a TLD of &lt;code&gt;.cghmn&lt;/code&gt; and &lt;code&gt;.retro&lt;/code&gt; to the internal DNS root server.

The Wireguard endpoint servers as the connection into the CGHMN from the outside internet on &lt;code&gt;66.170.190.194:42070&lt;/code&gt; for anyone that wishes to parttake the network. See [[Signup]] for more details on how to join.

==== Container 10401 (demo-cghmn-root-dns, VLAN4, 172.23.4.101) ====
This container, based on the absolutely tiny-footprinted Alpine image, hosts the BIND-based root DNS server for the internal CGHMN domains &lt;code&gt;.retro&lt;/code&gt; and &lt;code&gt;.cghmn&lt;/code&gt; together with the reverse DNS zone for the 172.23.0.0 network. It lives in the Core Services subnet and is reachable on port 53 for DNS queries from every other internal subnet. Zones are configured in the zone files under &lt;code&gt;/etc/bind/zones&lt;/code&gt; and loaded by the zone blocks in the &lt;code&gt;/etc/named.conf&lt;/code&gt; file.

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10401&lt;/code&gt; on the Proxmox host console.

==== Container 10402 (demo-cghmn-ca, VLAN4, 172.23.4.102) ====
This container, also based on Alpine, is hosting the custom Certificate Authority based on OpenSSL created and self-signed certificate files. It is currently constructed in a Root CA -&gt; Intermediate CA -&gt; Server Certificates structure, where the CA signed certificates of the intermediate CA, which then signs all certificates requested for servers and clients on the network. Clients thus should only need to install the CA certificate into their trusted keychain to have valid TLS connections to servers using certificates signed by this internal CA.

Clients can access a web server on &lt;code&gt;certs.cghmn:80&lt;/code&gt; or &lt;code&gt;172.23.4.102:80&lt;/code&gt; via plain HTTP to download the root CA and intermediate CA certificate files for installation on their retro machines. Note: This is not meant to be secure. When you add this root CA, we could pretend to be any server on the internet under any domain and any system that has the root CA or intermediate CA certificate installed will trust it. Don't add this on machines you would have personal data on or that you would let onto the public internet!

The /root directory of this container contains a script called &lt;code&gt;create-and-sign-server-csr.sh&lt;/code&gt; that, when run without any arguments, will ask a few questions on the command line and generate a signed TLS certificate in the root directory for the specified DNS names to make deployment of new TLS certificates a little easier. This requires the password of the private key of the intermediate CA, which again is currently stored in Sneps password manager but of course will be copied to a safe location to store passwords once available for the CGHMN.

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10402&lt;/code&gt; on the Proxmox host console.

==== Container 10403 (demo-cghmn-vxlan-endpoint, VLAN4, 172.23.4.103) ====
This container, another Alpine instance, connects all the VXLAN clients together under one virtual Linux bridge and is constructed with a couple if-up/if-down scripts and a Bash script to create new tunnels at &lt;code&gt;/opt/vxlan-scripts/create-vxlan-interface.sh&lt;/code&gt;. 

This script, when called like for example so: &lt;code&gt;create-vxlan-interface.sh 100.89.128.90&lt;/code&gt; will do the following:

# Find the first unused VXLAN ID
# Output the VXLAN ID for configuring a new VXLAN tunnel on the client side
# Add an interface configuration to &lt;code&gt;/etc/vxlan-interfaces/&lt;/code&gt; which is sourced by ifupdown
# Bring up that new VXLAN interface, which bridges it to the Global LAN bridge

after which the client with IP 100.89.128.90 can connect a VXLAN tunnel with the newly added VXLAN ID to their router and join the network.

This is still a very manual process, though one which will probably become more streamlined in the future of the CGHMN network, perhaps with some APIs and/or custom OpenWRT web interface *wink wink*.

This container is only reachable by the firewall itself and by the clients connecting their VXLAN bridge to port 4789 from the Wireguard tunnel, as it doesn't do any routing or hosting of services directly aside from the VXLAN endpoint.

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10403&lt;/code&gt; on the Proxmox host onsole.

==== Container 10404 (demo-cghmn-legacy-dns, VLAN4, 172.23.4.104) ====
This container, based on Alpine, runs a dnsmasq instance configured to look up certain DNS overrides either in the hosts file at &lt;code&gt;/etc/cghmn-dns-overrides&lt;/code&gt; or by including a dnsmasq configuration file from &lt;code&gt;/etc/dnsmasq-cghmn.d/*.conf&lt;/code&gt;. Any other requests it cannot resolve locally are forwarded to the Unbound DNS resolver running on the OPNsense router VM. This setup is used to create DNS overrides for existing domains to make old software, which is hardcoded to specific DNS entries, work again with custom servers hosted internally. 

Currently, there is no root password set, console access works either via key-based SSH or by entering &lt;code&gt;pct enter 10404&lt;/code&gt; on the Proxmox host console.


=== Proposed Organization of IDs and IPs ===
My (Sneps) idea behind Proxmox container and VM IDs are as follows:

'''101xx - 103xx''' are for Containers and VMs in the bridged layer 2 network, so any hosts that members want to run in the bridged network directly.

'''104xx - 107xx''' are for Containers and VMs in the Core Services VLAN4, so anything that is necessary for the operation of the CGHMN network.

'''108xx - 111xx''' are for Containers and VMs in the Servers VLAN8, so anything that members would choose to host on the CGHMN Proxmox.


For IPs, I left the first 10 IPs in each subnet reserved for things like routers, for example (perhaps a second router and a virtual IP for failover down the line?).

After that, the first half of the subnet (see above under Network Layout for the actual start and end of this range) is supposed to be reserved for any hosts that are set up with a fully static IP. This is entirely outside of the DHCP range to avoid any conflicts. That DHCP range then starts with the second half of the subnet and goes up to the last available host IP of each subnet.


=== Other Notes ===

* Currently, the advertised DNS server via DHCP is the included Unbound Server on the OPNsense instance. If we want to completely seal off clients and servers from the rest of the internet, we could directly point the clients towards our root DNS server for all requests.
* Currently, the OPNsense router does DHCP as it already has an IP in each VLAN and comes with a solid DHCP server that can also support failover out of the box (ISC DHCP). I (Snep) chose this route over a standalone DHCP server to avoid having a second container/VM in each subnet that solely does DHCP or DHCP proxying, mainly to keep the setup and maintenance work as low as possible.
* A customized OpenWRT image for the Gl.iNet MT300n and AR300n are currently being built and tested, which includes required packages and UCI configurations out of the box to make joining the network perhaps a little bit easier. Will update this page or create a new one and link to it once a working image exists!


=== Reserved static IPs ===

* '''VLAN1, 172.23.0.11:''' WIREGUARD-EXTERNAL (CursedSilicon)</text>
    <sha1>90a7e47f08fdfc87c034630ad5d226d675e48b55</sha1>
  </revision>
</page>
<page arvcontinue="20250506224236|158">
  <title>CGHMN 1.0</title>
  <ns>0</ns>
  <id>79</id>
  <revision>
    <id>169</id>
    <parentid>141</parentid>
    <timestamp>2025-05-11T02:33:13Z</timestamp>
    <contributor>
      <username>Ilostmybagel</username>
      <id>3</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="614" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
== Tracking sheet for "what would we want in a general 1.0 release" ==


Let's break these down by user just to keep division of labor easy

=== CursedSilicon suggestions ===


The main blocker currently is access to reliable fiber at /dev/hack. Gaining that should give us ample bandwidth to start allowing broader user access to the network generally

Maybe invite a selection of "retro networking" youtube folks (TheSerialPort, ClabRetro, etc) to help tire kick things? Serena also suggested federation of retro network service providers, so this could be a useful step.</text>
    <sha1>3be1831751723b6f82f45dcc70ff5f9bdddfdf5d</sha1>
  </revision>
</page>
<page arvcontinue="20250506224236|158">
  <title>Signup</title>
  <ns>0</ns>
  <id>75</id>
  <revision>
    <id>171</id>
    <parentid>124</parentid>
    <timestamp>2025-05-11T02:36:13Z</timestamp>
    <contributor>
      <username>Ilostmybagel</username>
      <id>3</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1078" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
So! You want to be a member of CompuGlobalHyperMegaNet?

Excellent! Here's how you sign up


Firstly you'll need to join the [https://discord.gg/TnpSG2P677 Cursed Silicon Discord].  

Ping one of our Mod staff and request access to the '''#compu-global-hyper-mega-net''' channel


After you've been granted access to the channel, @compu-global-hyper-mega-net and let us know what you'd like to build or run. A few helpful specifics 

* Do you have Systems Admin/Network Admin skills? Do you need help with the stuff you'd like to run?

* Are you volunteering as a single user or are you participating as part of a group?
* Are you intending to use CGHMN's hosting, or do you want to simply attach your own retro hardware to the network?
* What are the best ways we can contact you (usually just in case anything breaks) 

Once that's all sorted we'll help you get your project off the ground and running on the network as best we can. 

Once it's up and running though please keep in mind '''you will be responsible for maintaining it'''</text>
    <sha1>757860e6fc61288167d00584484155a565339547</sha1>
  </revision>
  <revision>
    <id>172</id>
    <parentid>171</parentid>
    <timestamp>2025-05-12T09:05:06Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Reworded things, added IRC</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1234" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
So! You want to be a member of CompuGlobalHyperMegaNet?

Excellent! Here's how you sign up


Firstly you'll need to either join the [https://discord.gg/TnpSG2P677 Cursed Silicon Discord].or connect to the IRC @ '''irc.cursedsilicon.net:6667''' and join channel '''#cghmn'''  

For '''Discord''' users, please @ the mod team and you'll be assigned the relevant user role.
 
After you've been granted access to the channel llet us know what you'd like to build or run. A few helpful specifics 

* Do you have Systems Admin/Network Admin skills? Do you need help with the stuff you'd like to run?

* Are you volunteering as a single user or are you participating as part of a group?
* Are you intending to use CGHMN's hosting, or do you want to simply attach your own retro hardware to the network?
* What are the best ways we can contact you (usually just in case anything breaks) 

Once that's all sorted we'll help you get your project off the ground and running on the network as best we can. 

Once it's up and running though please keep in mind '''you will be responsible for maintaining it!''' We provide network access (and infrastructure hosting) but can't run your pet project for you!</text>
    <sha1>367d95b88f8b4d72b6c9b0c43d5290b773bd7b18</sha1>
  </revision>
</page>
<page arvcontinue="20250506224236|158">
  <title>File:Example Certificate Script Run.png</title>
  <ns>6</ns>
  <id>86</id>
  <revision>
    <id>174</id>
    <timestamp>2025-05-15T20:09:27Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="115" xml:space="preserve">Terminal output of the Root CA Certificate creation script showing the domain example.retro receiving a certificate</text>
    <sha1>968f97e2757881f995ee3ebe25ec6e671cd20023</sha1>
  </revision>
</page>
<page arvcontinue="20250506224236|158">
  <title>CGHMN Certificate Authority</title>
  <ns>0</ns>
  <id>87</id>
  <revision>
    <id>175</id>
    <timestamp>2025-05-15T20:10:02Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <comment>Created page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5614" xml:space="preserve">=== The CGHMN Certificate Authority ===
... is used to create internal certificates for old SSL and TLS applications with our custom domains .cghmn and .retro, which cannot receive actual, real world publicly trusted certificates.

To trust those certificates, navigate to http://certs.cghmn, download the Root CA certificate and install it into your operating systems root CA store.

'''WARNING:''' Only do this on retro machines that are attached to the CGHMN, don't do this on modern machines with data you care for and websites you'd rather not have potentially [[wikipedia:Man-in-the-middle_attack|MITM]]'ed. Installing and trustig the Root CA certificate would allow us (or anyone that has access to the root CA public and private keys together with the signing password) to create whatever certificate we like for any domain name out there and fool your OS into thinking it can trust that self-signed certificate. 

Alternatively, you can always just click "Trust this page" or similar in your web browser and most applications that rely on SSL/TLS have some option to disable CA checking.

=== How to obtain a certificate for your .cghmn or .retro domain ===
If you'd like a certificate for your CGHMN internal domain, ping one of the admins in the Discord channel and pass along the following infos:

* Domain Name: The domain you'd like to receive a certificate for
* How to best send you your certificate, e.g. Discord DMs, E-Mail, some Messenger, Filesharing service etc., best not through a public channel
* Optionally:
** If you want a wildcard certificate, i.e. one certificate for the domain above and all subdomains underneath that domain (e.g. *.example.org)
** If you'd like the private key to be protected with a randomly generated password
** What two letter code to fill into the "Country" field of the certificate, default is "XX"
** What to fill into the "State or Province" field of the certificate, default is "Global"
** What to fill into the "Locality" field of the certificate, defaut is "The Internet"
** What to fill into the "Organization Name" field of the certificate, default is "Compu Global Hyper Mega Network"
** What to fill into the "Organizational Unit" field of the certificate, default is your username
** What to fill into the "E-Mail" field of the certificate, default is "complain@mail.cghmn"
** ''All of the above can be freely chosen and be whatever you like''

Then we'll create the certificate, private key and full chain certificate and send it over so you can install it into whatever service you like!

=== How to generate a certificate - For CGHMN Admins ===
[[File:Example Certificate Script Run.png|thumb|Script Example Output]]
To generate a members' certificate, &lt;code&gt;ssh&lt;/code&gt; or &lt;code&gt;pct enter&lt;/code&gt; into Container &lt;code&gt;10402&lt;/code&gt; with IP address &lt;code&gt;172.23.4.102&lt;/code&gt;. In the root directory should be a Bash script called &lt;code&gt;create-and-sign-server-csr.sh&lt;/code&gt;, run it with &lt;code&gt;bash /root/create-and-sign-server-csr.sh&lt;/code&gt;.

It will first ask you what the output files should be called, it's best to enter something that associates the file with the target domain or member, e.g. the domain itself or the members' username. It's recommended to only use alpha-numerical characters, dashes, underscores and dots.

Next, you're asked if the key shall be protected with a password. If the member didn't specify or doesn't want one, you can just press '''Enter''' on this step to select the default value of ''not'' using a password. Otherwise type '''y''' and press '''Enter''' to confirm, then generate a random password with a website, tool or password manager of your choice and input said password in the "Enter PEM pass phrase" prompt. The password needs to be at least 4 characters long!

The next step asks you for the hostnames of the certificate. Enter all hostnames you want the certificate to be valid for, e.g. &lt;code&gt;example.retro&lt;/code&gt;, &lt;code&gt;www.example.retro&lt;/code&gt; and &lt;code&gt;mail.example.retro&lt;/code&gt;. If the member requested a wildcard certificate, enter the base domain first, e.g. &lt;code&gt;example.retro&lt;/code&gt;, followed by the wildcard domain, e.g. &lt;code&gt;*.example.retro&lt;/code&gt;. Once all domain names are entered, press '''Ctrl+D''' to confirm.

If you've specified '''y''' at the question above if the private key should be password protected, you will next be asked to re-enter that password.

Next, you'll be asked for the Common Name, there enter the base domain for which the certificate is valid, e.g. '''example.retro'''.

Then, some certificate options can be set like Country, Organization and E-Mail assigned with the certificate, which are most of the optional details listed above that the member can specify if they like, which does not need to be real data, it can be whatever they like. Otherwise, just press '''Enter''' on the fields to select the predefined default values.

The next password requested from you is the Intermediate CA Signing Password, followed by two confirmations if you really really want to sign the new certificates with our intermediate CA. Input '''y''' and press '''Enter''' both times.

Now the certificate is created and ready for use, the script will tell you into which directory it has written the certificate files.

All that's left to do now is to SCP the files off the CA container and send them over to the member in a secure-ish fashion through their prefered channel. Don't send them in the Discord channel unless they're fine with it since it allows someone else to more easily impersonate their site, not that that's a huge concern in the CGHMN network, but still.</text>
    <sha1>9fde753c6539e3f73c78191bb51128c7c244c80e</sha1>
  </revision>
</page>
<page arvcontinue="20250506224236|158">
  <title>CGHMN DNS Information</title>
  <ns>0</ns>
  <id>88</id>
  <revision>
    <id>177</id>
    <timestamp>2025-05-16T00:02:53Z</timestamp>
    <contributor>
      <username>Talija</username>
      <id>10</id>
    </contributor>
    <comment>Initial post, creating to add a summary of the different DNS servers on the network.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3463" xml:space="preserve">== About this page ==
This page exists to document information about the DNS of CGHMN, and some of the complexities that comes with a DNS infrastructure made of up varying platforms across decades of the protocol's evolution.  See [[CGHMN-Demo-Network]] for detailed information about the underlying infrastructure 

== DNS Configuration Guide ==

=== Getting Started ===

==== Pointing to the right DNS server ====
CGHMN has several DNS servers in use for differing purposes.  The correct default DNS server you should be pointing at while getting started is 172.23.0.1.  This is the router, which then forwards the requests to the actual DNS.

==== What the different DNS servers are (or, is this thing on?) ====
CGHMN's DNS is configured such that there are three core servers that perform response modifications to allow the recreation of long defunct services, perform lookups, and act as the root name server for the network, which has two internal TLD (top level domain, like .com or .net) on it.

===== 172.23.4.101 - ns1.cghmn =====
This is the root name server for the .retro and .cghmn TLDs, as well as the 23.172.in-addr.arpa and 96.100.in-addr.arpa reverse lookup zones.  This server exists to delegate domains to members of CGHMN, and serve as the name server for the internal network.  This server is useful to perform a &lt;code&gt;dig&lt;/code&gt; or &lt;code&gt;nslookup&lt;/code&gt; against if you want to see if a subdomain has been delegated, for example:

&lt;code&gt;dig ns example.retro. @172.23.4.101&lt;/code&gt;

or
 nslookup
 
 &gt; server 172.23.4.101
 
 &gt; set type=ns
 
 &gt; example.retro.
This server does not perform lookups.  It is currently running BIND.

===== 172.23.4.105 =====
This is the recursive lookup server for the network.  It is configured to recursively look up all requests for CGHMN domains, starting with ns1.cghmn, and then moving up based on delegations to member servers.  Regular lookups still take place against real TLDs, if something needs to be pulled off the internet.  This server is currently running BIND.  This server is useful to use &lt;code&gt;dig&lt;/code&gt; or &lt;code&gt;nslookup&lt;/code&gt; against if you wish to see if your domain is resolving on the network after it has been delegated to you.

&lt;code&gt;dig a test.example.retro. @172.23.4.105&lt;/code&gt;

or
 nslookup
 
 &gt; server 172.23.4.105
 
 &gt; set type=a
 
 &gt; test.example.retro.

===== 172.23.4.104 - legacydns.cghmhn =====
This is a dnsmasq server that is currently being used to perform modifications to DNS answers, by pulling from a list of servers that need to be faked in order to make old software, such as AIM, work correctly.  This server overrides the DNS answer with these responses, so all relevant DNS records need to be added.  Please ask if there is a service you would like added to the network that requires this kind of override.  Otherwise, it just forwards the questions to the recursive lookup server 172.23.4.105.  This server is useful to test against if you are having trouble connecting to a legacy service that utilizes hard coded DNS.

&lt;code&gt;dig cname login.oscar.aol.com.&lt;/code&gt;

or
 nslookup
 
 &gt; server 172.23.4.104
 
 &gt; set type=cname
 
 &gt; login.oscar.aol.com.

===== 172.23.0.1 =====
This is the core router for the network, which also serves as a DNS forwarding.  It is currently forwarding all traffic to legacydns.cghmn, and performs no additional lookups or translation.  This server is useful to test against for any purpose.
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>04c4c50845f8a64d30dee8d7f7544fa01be720bb</sha1>
  </revision>
  <revision>
    <id>181</id>
    <parentid>177</parentid>
    <timestamp>2025-05-16T00:27:41Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Minor formatting tweak, added info about legacy DNS</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3666" xml:space="preserve">== About this page ==
This page exists to document information about the DNS of CGHMN, and some of the complexities that comes with a DNS infrastructure made of up varying platforms across decades of the protocol's evolution.  See [[CGHMN-Demo-Network]] for detailed information about the underlying infrastructure 

== DNS Configuration Guide ==

=== Getting Started ===

==== Pointing to the right DNS server ====
CGHMN has several DNS servers in use for differing purposes.  '''The correct default DNS server you should be pointing at while getting started is 172.23.0.1'''.  This is the router, which then forwards the requests to the actual DNS.

==== What the different DNS servers are (or, is this thing on?) ====
CGHMN's DNS is configured such that there are three core servers that perform response modifications to allow the recreation of long defunct services, perform lookups, and act as the root name server for the network, which has two internal TLD (top level domain, like .com or .net) on it.

===== 172.23.4.101 - ns1.cghmn =====
This is the root name server for the .retro and .cghmn TLDs, as well as the 23.172.in-addr.arpa and 96.100.in-addr.arpa reverse lookup zones.  This server exists to delegate domains to members of CGHMN, and serve as the name server for the internal network.  This server is useful to perform a &lt;code&gt;dig&lt;/code&gt; or &lt;code&gt;nslookup&lt;/code&gt; against if you want to see if a subdomain has been delegated, for example:

&lt;code&gt;dig ns example.retro. @172.23.4.101&lt;/code&gt;

or
 nslookup
 
 &gt; server 172.23.4.101
 
 &gt; set type=ns
 
 &gt; example.retro.
This server does not perform lookups.  It is currently running BIND.

===== 172.23.4.105 =====
This is the recursive lookup server for the network.  It is configured to recursively look up all requests for CGHMN domains, starting with ns1.cghmn, and then moving up based on delegations to member servers.  Regular lookups still take place against real TLDs, if something needs to be pulled off the internet.  This server is currently running BIND.  This server is useful to use &lt;code&gt;dig&lt;/code&gt; or &lt;code&gt;nslookup&lt;/code&gt; against if you wish to see if your domain is resolving on the network after it has been delegated to you.

&lt;code&gt;dig a test.example.retro. @172.23.4.105&lt;/code&gt;

or
 nslookup
 
 &gt; server 172.23.4.105
 
 &gt; set type=a
 
 &gt; test.example.retro.

===== 172.23.4.104 - legacydns.cghmhn =====
This is a dnsmasq server that is currently being used to perform modifications to DNS answers, by pulling from a list of servers that need to be faked in order to make old software, such as AIM, work correctly.  This server overrides the DNS answer with these responses, so all relevant DNS records need to be added. The rationale for this is that instead of a user modifying their hosts file (which can be dozens of different DNS addresses long) we can simply return addresses that correspond within the network.  Please ask if there is a service you would like added to the network that requires this kind of override.  Otherwise, it just forwards the questions to the recursive lookup server 172.23.4.105.  This server is useful to test against if you are having trouble connecting to a legacy service that utilizes hard coded DNS.

&lt;code&gt;dig cname login.oscar.aol.com.&lt;/code&gt;

or
 nslookup
 
 &gt; server 172.23.4.104
 
 &gt; set type=cname
 
 &gt; login.oscar.aol.com.

===== 172.23.0.1 =====
This is the core router for the network, which also serves as a DNS forwarding.  It is currently forwarding all traffic to legacydns.cghmn, and performs no additional lookups or translation.  This server is useful to test against for any purpose.
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>303ebb8c63406765f2b67913be32a9974ddebdff</sha1>
  </revision>
  <revision>
    <id>182</id>
    <parentid>181</parentid>
    <timestamp>2025-05-16T02:31:05Z</timestamp>
    <contributor>
      <username>Talija</username>
      <id>10</id>
    </contributor>
    <comment>Added hosting your own and weird quirks</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6482" xml:space="preserve">== About this page ==
This page exists to document information about the DNS of CGHMN, and some of the complexities that comes with a DNS infrastructure made of up varying platforms across decades of the protocol's evolution.  See [[CGHMN-Demo-Network]] for detailed information about the underlying infrastructure 

== DNS Configuration Guide ==

=== Getting Started ===

==== Pointing to the right DNS server ====
CGHMN has several DNS servers in use for differing purposes.  '''The correct default DNS server you should be pointing at while getting started is 172.23.0.1'''.  This is the router, which then forwards the requests to the actual DNS.

==== What the different DNS servers are (or, is this thing on?) ====
CGHMN's DNS is configured such that there are three core servers that perform response modifications to allow the recreation of long defunct services, perform lookups, and act as the root name server for the network, which has two internal TLD (top level domain, like .com or .net) on it.

===== 172.23.4.101 - ns1.cghmn =====
This is the root name server for the .retro and .cghmn TLDs, as well as the 23.172.in-addr.arpa and 96.100.in-addr.arpa reverse lookup zones.  This server exists to delegate domains to members of CGHMN, and serve as the name server for the internal network.  This server is useful to perform a &lt;code&gt;dig&lt;/code&gt; or &lt;code&gt;nslookup&lt;/code&gt; against if you want to see if a subdomain has been delegated, for example:

&lt;code&gt;dig ns example.retro. @172.23.4.101&lt;/code&gt;

or
 nslookup
 
 &gt; server 172.23.4.101
 
 &gt; set type=ns
 
 &gt; example.retro.
This server does not perform lookups.  It is currently running BIND.

===== 172.23.4.105 =====
This is the recursive lookup server for the network.  It is configured to recursively look up all requests for CGHMN domains, starting with ns1.cghmn, and then moving up based on delegations to member servers.  Regular lookups still take place against real TLDs, if something needs to be pulled off the internet.  This server is currently running BIND.  This server is useful to use &lt;code&gt;dig&lt;/code&gt; or &lt;code&gt;nslookup&lt;/code&gt; against if you wish to see if your domain is resolving on the network after it has been delegated to you.

&lt;code&gt;dig a test.example.retro. @172.23.4.105&lt;/code&gt;

or
 nslookup
 
 &gt; server 172.23.4.105
 
 &gt; set type=a
 
 &gt; test.example.retro.

===== 172.23.4.104 - legacydns.cghmhn =====
This is a dnsmasq server that is currently being used to perform modifications to DNS answers, by pulling from a list of servers that need to be faked in order to make old software, such as AIM, work correctly.  This server overrides the DNS answer with these responses, so all relevant DNS records need to be added. The rationale for this is that instead of a user modifying their hosts file (which can be dozens of different DNS addresses long) we can simply return addresses that correspond within the network.  Please ask if there is a service you would like added to the network that requires this kind of override.  Otherwise, it just forwards the questions to the recursive lookup server 172.23.4.105.  This server is useful to test against if you are having trouble connecting to a legacy service that utilizes hard coded DNS.

&lt;code&gt;dig cname login.oscar.aol.com.&lt;/code&gt;

or
 nslookup
 
 &gt; server 172.23.4.104
 
 &gt; set type=cname
 
 &gt; login.oscar.aol.com.

===== 172.23.0.1 =====
This is the core router for the network, which also serves as a DNS forwarding.  It is currently forwarding all traffic to legacydns.cghmn, and performs no additional lookups or translation.  This server is useful to test against for any purpose.

== Hosting Your Own DNS Name Server ==

=== About self-hosting ===
CGHMN can host member DNS zones on its nameserver, however it is welcome and even encouraged for them to explore setting up their own DNS name server for their subnet.  This can be done with most DNS server software, provided they can be recursively looked up against by BIND.  Please note that if you intend to run old Microsoft DNS, you will need to let us know that you are running it, as exceptions to the lookup procedure need to be added to the 172.23.4.105 server.

You will need to reach out to CGHMN and let us know you want to host your domain, and give us the domain, NS record, A record, and IP address of the DNS server.

=== What you need ===

==== A server ====
You will need a computer connected to CGHMN, running a DNS server software that is able to act as an authoritative name server.  It will need to have UDP port 53 and TCP port 53 allowed in its firewall.  You do not need a lot of power, but it should be fairly reliable as everything will depend on it to find your servers and services.

==== A SOA record ====
You will need a SOA (Start of Authority) record, this is the record that tells other DNS servers "I am in charge of this domain and here is the information about it".  This record will need to be pointed to an NS (Name Server) record.

==== A NS record ====
You will need a NS record, this is the record that says "this is where you ask about this domain".  This record should point at an A record.

==== An A record ====
You will need an A record, this is the record that maps the name of the DNS server to an IP address.  This should be the FQDN (Fully Qualified Domain Name) of the DNS server, and the IP address it is listening to.

==== Summary ====
Your server will need to be configured as an authoritative name server.  To do this, it must run a DNS name server software, which should have a zone containing an the SOA, which points at the NS, which points at the A.

== DNS Quirks ==

=== Windows DNS ===
Old Windows DNS servers will misbehave when BIND's recursive lookup server attempts to do a lookup against them, and will end in failure.  The way around this is to disable edns lookups against this particular server in the BIND configuration.  Bind is supposed to attempt again with edns disabled but it seems with Windows DNS specifically to fail.

=== DNS manipulation with multiple RR types ===
If a record is being looked up, and this record was once an A record, but still exists and is now a CNAME record, you will have an issue where the lookup will work with tools, but fail with actual lookups.  This is because the CNAME record being returned from the real DNS server will take precedent over the fake A record.  To resolve this issue, you have to fake both the CNAME and the A record.
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>0e7323016f7c3cfb40e8fbe276a844eab9ef83ea</sha1>
  </revision>
  <revision>
    <id>183</id>
    <parentid>182</parentid>
    <timestamp>2025-05-16T06:49:26Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>Added info about default DNS being 100.89.128.0 in the WG tunnel</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6547" xml:space="preserve">== About this page ==
This page exists to document information about the DNS of CGHMN, and some of the complexities that comes with a DNS infrastructure made of up varying platforms across decades of the protocol's evolution.  See [[CGHMN-Demo-Network]] for detailed information about the underlying infrastructure 

== DNS Configuration Guide ==

=== Getting Started ===

==== Pointing to the right DNS server ====
CGHMN has several DNS servers in use for differing purposes.  '''The correct default DNS server you should be pointing at while getting started is 172.23.0.1 from the core network, or 100.89.128.0 from the Wireguard tunnel'''.  This is the router, which then forwards the requests to the actual DNS.

==== What the different DNS servers are (or, is this thing on?) ====
CGHMN's DNS is configured such that there are three core servers that perform response modifications to allow the recreation of long defunct services, perform lookups, and act as the root name server for the network, which has two internal TLD (top level domain, like .com or .net) on it.

===== 172.23.4.101 - ns1.cghmn =====
This is the root name server for the .retro and .cghmn TLDs, as well as the 23.172.in-addr.arpa and 96.100.in-addr.arpa reverse lookup zones.  This server exists to delegate domains to members of CGHMN, and serve as the name server for the internal network.  This server is useful to perform a &lt;code&gt;dig&lt;/code&gt; or &lt;code&gt;nslookup&lt;/code&gt; against if you want to see if a subdomain has been delegated, for example:

&lt;code&gt;dig ns example.retro. @172.23.4.101&lt;/code&gt;

or
 nslookup
 
 &gt; server 172.23.4.101
 
 &gt; set type=ns
 
 &gt; example.retro.
This server does not perform lookups.  It is currently running BIND.

===== 172.23.4.105 =====
This is the recursive lookup server for the network.  It is configured to recursively look up all requests for CGHMN domains, starting with ns1.cghmn, and then moving up based on delegations to member servers.  Regular lookups still take place against real TLDs, if something needs to be pulled off the internet.  This server is currently running BIND.  This server is useful to use &lt;code&gt;dig&lt;/code&gt; or &lt;code&gt;nslookup&lt;/code&gt; against if you wish to see if your domain is resolving on the network after it has been delegated to you.

&lt;code&gt;dig a test.example.retro. @172.23.4.105&lt;/code&gt;

or
 nslookup
 
 &gt; server 172.23.4.105
 
 &gt; set type=a
 
 &gt; test.example.retro.

===== 172.23.4.104 - legacydns.cghmhn =====
This is a dnsmasq server that is currently being used to perform modifications to DNS answers, by pulling from a list of servers that need to be faked in order to make old software, such as AIM, work correctly.  This server overrides the DNS answer with these responses, so all relevant DNS records need to be added. The rationale for this is that instead of a user modifying their hosts file (which can be dozens of different DNS addresses long) we can simply return addresses that correspond within the network.  Please ask if there is a service you would like added to the network that requires this kind of override.  Otherwise, it just forwards the questions to the recursive lookup server 172.23.4.105.  This server is useful to test against if you are having trouble connecting to a legacy service that utilizes hard coded DNS.

&lt;code&gt;dig cname login.oscar.aol.com.&lt;/code&gt;

or
 nslookup
 
 &gt; server 172.23.4.104
 
 &gt; set type=cname
 
 &gt; login.oscar.aol.com.

===== 172.23.0.1 =====
This is the core router for the network, which also serves as a DNS forwarding.  It is currently forwarding all traffic to legacydns.cghmn, and performs no additional lookups or translation.  This server is useful to test against for any purpose.

== Hosting Your Own DNS Name Server ==

=== About self-hosting ===
CGHMN can host member DNS zones on its nameserver, however it is welcome and even encouraged for them to explore setting up their own DNS name server for their subnet.  This can be done with most DNS server software, provided they can be recursively looked up against by BIND.  Please note that if you intend to run old Microsoft DNS, you will need to let us know that you are running it, as exceptions to the lookup procedure need to be added to the 172.23.4.105 server.

You will need to reach out to CGHMN and let us know you want to host your domain, and give us the domain, NS record, A record, and IP address of the DNS server.

=== What you need ===

==== A server ====
You will need a computer connected to CGHMN, running a DNS server software that is able to act as an authoritative name server.  It will need to have UDP port 53 and TCP port 53 allowed in its firewall.  You do not need a lot of power, but it should be fairly reliable as everything will depend on it to find your servers and services.

==== A SOA record ====
You will need a SOA (Start of Authority) record, this is the record that tells other DNS servers "I am in charge of this domain and here is the information about it".  This record will need to be pointed to an NS (Name Server) record.

==== A NS record ====
You will need a NS record, this is the record that says "this is where you ask about this domain".  This record should point at an A record.

==== An A record ====
You will need an A record, this is the record that maps the name of the DNS server to an IP address.  This should be the FQDN (Fully Qualified Domain Name) of the DNS server, and the IP address it is listening to.

==== Summary ====
Your server will need to be configured as an authoritative name server.  To do this, it must run a DNS name server software, which should have a zone containing an the SOA, which points at the NS, which points at the A.

== DNS Quirks ==

=== Windows DNS ===
Old Windows DNS servers will misbehave when BIND's recursive lookup server attempts to do a lookup against them, and will end in failure.  The way around this is to disable edns lookups against this particular server in the BIND configuration.  Bind is supposed to attempt again with edns disabled but it seems with Windows DNS specifically to fail.

=== DNS manipulation with multiple RR types ===
If a record is being looked up, and this record was once an A record, but still exists and is now a CNAME record, you will have an issue where the lookup will work with tools, but fail with actual lookups.  This is because the CNAME record being returned from the real DNS server will take precedent over the fake A record.  To resolve this issue, you have to fake both the CNAME and the A record.
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>397a12b8d3755597133d2ad81e1f616c67aa3c0a</sha1>
  </revision>
</page>
<page arvcontinue="20250506224236|158">
  <title>Talk:CGHMN DNS Information</title>
  <ns>1</ns>
  <id>89</id>
  <revision>
    <id>178</id>
    <timestamp>2025-05-16T00:05:35Z</timestamp>
    <contributor>
      <username>Talija</username>
      <id>10</id>
    </contributor>
    <comment>general to-do</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="181" xml:space="preserve">To be added: information about DNS quirks, particularly:
-DNS response alteration setup when records other than an A record are in use
-BIND recursive lookup with old Windows Server</text>
    <sha1>644c199714e495c24df053ca6f162861f947802b</sha1>
  </revision>
  <revision>
    <id>179</id>
    <parentid>178</parentid>
    <timestamp>2025-05-16T00:06:51Z</timestamp>
    <contributor>
      <username>Talija</username>
      <id>10</id>
    </contributor>
    <minor/>
    <comment>fixing formatting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="224" xml:space="preserve">&lt;html&gt;
&lt;body&gt;
&lt;pre&gt;
To be added: information about DNS quirks, particularly:
-DNS response alteration setup when records other than an A record are in use
-BIND recursive lookup with old Windows Server
&lt;/pre&gt;
&lt;/body&gt;
&lt;/html&gt;</text>
    <sha1>f3a894308fb7c168d85c844d2e48ba4ba7e6a406</sha1>
  </revision>
  <revision>
    <id>180</id>
    <parentid>179</parentid>
    <timestamp>2025-05-16T00:07:09Z</timestamp>
    <contributor>
      <username>Talija</username>
      <id>10</id>
    </contributor>
    <minor/>
    <comment>one last fix...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="194" xml:space="preserve">&lt;pre&gt;
To be added: information about DNS quirks, particularly:
-DNS response alteration setup when records other than an A record are in use
-BIND recursive lookup with old Windows Server
&lt;/pre&gt;</text>
    <sha1>57c4bd2d56ac217e0419e0557caf4dab1ac4e14d</sha1>
  </revision>
</page>
<page arvcontinue="20250506224236|158">
  <title>AIM Clients</title>
  <ns>0</ns>
  <id>90</id>
  <revision>
    <id>196</id>
    <timestamp>2025-06-03T02:09:15Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested  Currently testing is done under Ubuntu 5.04 (i386) because 4.10 had weird SMP issues in Proxmox   This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But just act as a guide  TESTED WORKING  - gAIM"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="369" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Currently testing is done under Ubuntu 5.04 (i386) because 4.10 had weird SMP issues in Proxmox 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But just act as a guide

TESTED WORKING

- gAIM</text>
    <sha1>7c441bc819b90ff917fd1449ff6d5f15d23edc3c</sha1>
  </revision>
  <revision>
    <id>197</id>
    <parentid>196</parentid>
    <timestamp>2025-06-03T02:30:13Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1105" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Currently testing is done under Ubuntu 5.04 (i386) because 4.10 had weird SMP issues in Proxmox 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But just act as a guide

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

'''Older clients presumably work but are untested'''

'''&lt;u&gt;iChat ??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox&lt;/u&gt;'''

=== Linux ===
gAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. Bug filed</text>
    <sha1>3ce40ed6693a85e0720b2dbce87b03e3242920fd</sha1>
  </revision>
  <revision>
    <id>198</id>
    <parentid>197</parentid>
    <timestamp>2025-06-03T04:07:20Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3474" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Currently testing is done under Ubuntu 5.04 (i386) because 4.10 had weird SMP issues in Proxmox 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But just act as a guide

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
Adium X 1.0.6 (x86) works!
Adium 1.3.10 (x86) works!

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

=== Linux ===


gAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed]

TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some strange reason?

== TESTED '''NOT''' WORKING ==


'''Windows'''

Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - Packet dump available here

'''Mac'''

Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - Packet dump available here


'''Linux'''

Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - Packet dump available here

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - Packet dump available here

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - Packet dump available here

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - Packet dump available here


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>f84ce06a958974c8ea8558c06230c166c9fd8928</sha1>
  </revision>
  <revision>
    <id>199</id>
    <parentid>198</parentid>
    <timestamp>2025-06-03T04:12:24Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3544" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Currently testing is done under Ubuntu 5.04 (i386) because 4.10 had weird SMP issues in Proxmox 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But just act as a guide

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
Adium X 1.0.6 (x86) works! (PPC untested but presumed working)

Adium 1.3.10 (x86) works! (PPC untested but presumed working)

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

=== Linux gAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed] ===
TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some strange reason?

== TESTED '''NOT''' WORKING ==


'''Windows'''

Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - Packet dump available here

'''Mac'''

Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - Packet dump available here


'''Linux'''

Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - Packet dump available here

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - Packet dump available here

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - Packet dump available here

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - Packet dump available here


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>85a19a935d2ec0627315f5db4d654a9d1818b07b</sha1>
  </revision>
  <revision>
    <id>200</id>
    <parentid>199</parentid>
    <timestamp>2025-06-03T04:14:22Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3670" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Currently testing is done under Ubuntu 5.04 (i386) because 4.10 had weird SMP issues in Proxmox 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But should give users a general direction for further testing


Submissions are also welcome. Please feel free to email me or send me a message on Mastodon

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
Adium X 1.0.6 (x86) works! (PPC untested but presumed working)

Adium 1.3.10 (x86) works! (PPC untested but presumed working)

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

=== Linux ===
gAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed]

TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some reason?

== TESTED '''NOT''' WORKING ==


'''Windows'''

Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - Packet dump available here

'''Mac'''

Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - Packet dump available here


'''Linux'''

Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - Packet dump available here

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - Packet dump available here

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - Packet dump available here

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - Packet dump available here


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>25276be6e7bf103916abb7a85395c467bfdbb446</sha1>
  </revision>
  <revision>
    <id>201</id>
    <parentid>200</parentid>
    <timestamp>2025-06-03T04:14:52Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3671" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Currently testing is done under Ubuntu 5.04 (i386) because 4.10 had weird SMP issues in Proxmox 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But should give users a general direction for further testing

Submissions are also welcome. Please feel free to email me or send me a message on Mastodon

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
Adium X 1.0.6 (x86) works! (PPC untested but presumed working)

Adium 1.3.10 (x86) works! (PPC untested but presumed working)

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

=== Linux ===
gAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed]

TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some reason?

== TESTED '''NOT''' WORKING ==


'''Windows'''

Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - Packet dump available here

'''Mac'''

Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - Packet dump available here


'''Linux'''

Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - Packet dump available here

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - Packet dump available here

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - Packet dump available here

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - Packet dump available here


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>8e4c4f4583b19c1c29aabf134d9648300d75f908</sha1>
  </revision>
  <revision>
    <id>202</id>
    <parentid>201</parentid>
    <timestamp>2025-06-03T05:33:15Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3949" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Currently testing is done under Ubuntu 5.04 (i386) because 4.10 had weird SMP issues in Proxmox 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But should give users a general direction for further testing

Submissions are also welcome. Please feel free to email me or send me a message on Mastodon

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
Adium X 1.0.6 (x86) works! (PPC untested but presumed working)

Adium 1.3.10 (x86) works! (PPC untested but presumed working)

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

=== Linux ===
gAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed]

TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some reason?

== TESTED '''NOT''' WORKING ==


'''Windows'''

Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

'''Mac'''

Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


'''Linux'''

Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>8c556d1b30436e9bfd3f853614744dd4e6f23f6d</sha1>
  </revision>
  <revision>
    <id>203</id>
    <parentid>202</parentid>
    <timestamp>2025-06-03T05:38:06Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4107" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Windows testing is done on a Windows XP (32-bit) virtual machine with all updates applied  

Mac testing is done on OS X 10.6.8 via Proxmox 

Linux testing is done on Ubuntu 5.04 (32-bit) via Proxmox but may be augmented in future with different distros 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But should give users a general direction for further testing

Submissions are also welcome. Please feel free to email me or send me a message on Mastodon

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
Adium X 1.0.6 (x86) works! (PPC untested but presumed working)

Adium 1.3.10 (x86) works! (PPC untested but presumed working)

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

=== Linux ===
gAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed]

TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some reason?

== TESTED '''NOT''' WORKING ==


'''Windows'''

Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

'''Mac'''

Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


'''Linux'''

Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>9e18b668a65b3908683ffa858eaef2f7df65ae02</sha1>
  </revision>
  <revision>
    <id>204</id>
    <parentid>203</parentid>
    <timestamp>2025-06-03T05:40:06Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4276" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Windows testing is done on a Windows XP (32-bit) virtual machine with all updates applied  

Mac testing is done on OS X 10.6.8 via Proxmox 

Linux testing is done on Ubuntu 5.04 (32-bit) via Proxmox but may be augmented in future with different distros 

'''All testing was performed on [[Compu-Global-Hyper-Mega-Net|CGHMN]] to simplify packet captures. IP addresses do not reflect the ones used by regular RAS clients''' 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But should give users a general direction for further testing

Submissions are also welcome. Please feel free to email me or send me a message on Mastodon

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
Adium X 1.0.6 (x86) works! (PPC untested but presumed working)

Adium 1.3.10 (x86) works! (PPC untested but presumed working)

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

=== Linux ===
gAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed]

TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some reason?

== TESTED '''NOT''' WORKING ==


'''Windows'''

Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

'''Mac'''

Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


'''Linux'''

Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>1a0fc13f351f621bc2dd4aa0c528c25af5351d35</sha1>
  </revision>
  <revision>
    <id>205</id>
    <parentid>204</parentid>
    <timestamp>2025-06-03T21:32:13Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4358" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Windows testing is done on a Windows XP (32-bit) virtual machine with all updates applied  

Mac testing is done on OS X 10.6.8 via Proxmox 

Linux testing is done on Ubuntu 5.04 (32-bit) via Proxmox but may be augmented in future with different distros 

'''All testing was performed on [[Compu-Global-Hyper-Mega-Net|CGHMN]] to simplify packet captures. IP addresses do not reflect the ones used by regular RAS clients''' 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But should give users a general direction for further testing

Submissions are also welcome. Please feel free to email me or send me a message on Mastodon

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
Adium X 1.0.6 (x86) works! (PPC untested but presumed working)

Adium 1.3.10 (x86) works! (PPC untested but presumed working)

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

iChat on OS X Leopard (PPC or x86 unspecified) works!

AIM for OS 9 (PPC) works!

=== Linux ===
gAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed]

TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some reason?

== TESTED '''NOT''' WORKING ==


'''Windows'''

Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

'''Mac'''

Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


'''Linux'''

Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>9ff15546607e5440ccdc7e79e85bd4ff24ae0980</sha1>
  </revision>
  <revision>
    <id>206</id>
    <parentid>205</parentid>
    <timestamp>2025-06-05T04:23:40Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4358" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Windows testing is done on a Windows XP (32-bit) virtual machine with all updates applied  

Mac testing is done on OS X 10.6.8 via Proxmox 

Linux testing is done on Ubuntu 5.04 (32-bit) via Proxmox but may be augmented in future with different distros 

'''All testing was performed on [[Compu-Global-Hyper-Mega-Net|CGHMN]] to simplify packet captures. IP addresses do not reflect the ones used by regular RAS clients''' 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But should give users a general direction for further testing

Submissions are also welcome. Please feel free to email me or send me a message on Mastodon

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
Adium X 1.0.6 (x86) works! (PPC untested but presumed working)

Adium 1.3.10 (x86) works! (PPC untested but presumed working)

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

iChat on OS X Leopard (PPC or x86 unspecified) works!

AIM for OS 9 (PPC) works!

=== Linux ===
GAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed]

TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some reason?

== TESTED '''NOT''' WORKING ==


'''Windows'''

Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

'''Mac'''

Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


'''Linux'''

Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>3211fe93720e170b9d8e9bd16079378d032573d8</sha1>
  </revision>
</page>
<page arvcontinue="20250606090135|208">
  <title>CGHMN-IP-Allocations</title>
  <ns>0</ns>
  <id>77</id>
  <revision>
    <id>208</id>
    <parentid>207</parentid>
    <timestamp>2025-06-06T09:01:35Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2803" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| Unknown
|100.89.128.10
|100.96.10.0/24
| -
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>d753dc998cb860c3ec742ff4e6b8f393949ddb82</sha1>
  </revision>
  <revision>
    <id>214</id>
    <parentid>208</parentid>
    <timestamp>2025-06-12T19:25:03Z</timestamp>
    <contributor>
      <username>Gothpanda</username>
      <id>12</id>
    </contributor>
    <minor/>
    <comment>Edited member information</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2823" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>7b2acd725139c301d091677ff6b0700f7c5cca19</sha1>
  </revision>
  <revision>
    <id>215</id>
    <parentid>214</parentid>
    <timestamp>2025-06-14T20:27:08Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Add my media server to IP allocations</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2900" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|''kira.loganius.retro''
|172.23.0.52
|DNS not set up yet.
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>0f52909ac5b5f7efeb33426363d784f0005e14db</sha1>
  </revision>
  <revision>
    <id>216</id>
    <parentid>215</parentid>
    <timestamp>2025-06-14T20:29:37Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <minor/>
    <comment>DNS for kira.loganius.retro is now online.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2887" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>8a77c97859377d1e2030c9ad61b43142485f5ada</sha1>
  </revision>
  <revision>
    <id>217</id>
    <parentid>216</parentid>
    <timestamp>2025-06-15T06:00:45Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>Added cursed's mail server IP dibs</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2963" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|''Cursed''
|''-''
|''-''
|''172.23.0.69''
|''Future CGHMN Mail Server''
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>edeb43f52860954b1ad1cdb6cbc8bf3bb6e93fb2</sha1>
  </revision>
  <revision>
    <id>224</id>
    <parentid>217</parentid>
    <timestamp>2025-06-24T18:19:33Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Add documentation for a couple allocations that were never added to the wiki.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3139" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|''Cursed''
|''-''
|''-''
|''172.23.0.69''
|''Future CGHMN Mail Server''
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>49ef639f9ec30750205f6500c019420e4fdec993</sha1>
  </revision>
  <revision>
    <id>225</id>
    <parentid>224</parentid>
    <timestamp>2025-06-24T18:32:24Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Added Spaztron's domain</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3286" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|''Spaztron64''
|''arcesia.retro''
|''Unknown''
|''100.96.17.105''
|Something is wrong with the DNS atm, but adding this so it isn't forgotten.
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|''Cursed''
|''-''
|''-''
|''172.23.0.69''
|''Future CGHMN Mail Server''
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>54726eb67055cd7936936d99aeae1f840109a6e3</sha1>
  </revision>
  <revision>
    <id>226</id>
    <parentid>225</parentid>
    <timestamp>2025-06-24T21:49:10Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>we figured out who owns what IPs :D</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3478" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|''Spaztron64''
|''arcesia.retro''
|''Unknown''
|''100.96.17.105''
|Something is wrong with the DNS atm, but adding this so it isn't forgotten.
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|''Cursed''
|''-''
|''-''
|''172.23.0.69''
|''Future CGHMN Mail Server''
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>5c8cb7fa4f3d4dbd091cc264d200de035436962e</sha1>
  </revision>
  <revision>
    <id>227</id>
    <parentid>226</parentid>
    <timestamp>2025-06-24T22:22:32Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Added Nicuuut's delegated domain and CGHMN services</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3645" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|''Spaztron64''
|''arcesia.retro''
|''Unknown''
|''100.96.17.105''
|Something is wrong with the DNS atm, but adding this so it isn't forgotten.
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|''Cursed''
|''-''
|''-''
|''172.23.0.69''
|''Future CGHMN Mail Server''
|-
|Nicuuut
|103
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|124
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>f2376fedf7afa5306b2d40db5b9394fc36b582f5</sha1>
  </revision>
  <revision>
    <id>228</id>
    <parentid>227</parentid>
    <timestamp>2025-06-24T22:23:45Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <minor/>
    <comment>fixed VM IDs for Nicuuut</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3645" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|''Spaztron64''
|''arcesia.retro''
|''Unknown''
|''100.96.17.105''
|Something is wrong with the DNS atm, but adding this so it isn't forgotten.
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|''Cursed''
|''-''
|''-''
|''172.23.0.69''
|''Future CGHMN Mail Server''
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>e1c8b31aaf534190a2bcdc5de7fa39395130fe70</sha1>
  </revision>
  <revision>
    <id>230</id>
    <parentid>228</parentid>
    <timestamp>2025-06-25T21:47:42Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Add oohay.retro to the list of delegated domains</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3709" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|''Spaztron64''
|''arcesia.retro''
|''Unknown''
|''100.96.17.105''
|Something is wrong with the DNS atm, but adding this so it isn't forgotten.
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|''Cursed''
|''-''
|''-''
|''172.23.0.69''
|''Future CGHMN Mail Server''
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>54b8055e5569d5493ba1841576d9a8d8f1eaefb3</sha1>
  </revision>
  <revision>
    <id>232</id>
    <parentid>230</parentid>
    <timestamp>2025-06-26T01:14:04Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Added 404.retro to the member delegated domains</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3814" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|''Spaztron64''
|''arcesia.retro''
|''Unknown''
|''100.96.17.105''
|Something is wrong with the DNS atm, but adding this so it isn't forgotten.
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|''Harry''
|''404.retro''
|''ns.404.retro''
|''100.96.18.254''
|No DNS server on the member side yet.
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|''Cursed''
|''-''
|''-''
|''172.23.0.69''
|''Future CGHMN Mail Server''
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>e7ec85e55ed004afd254283a0438b9b0127af97d</sha1>
  </revision>
  <revision>
    <id>233</id>
    <parentid>232</parentid>
    <timestamp>2025-06-26T03:30:29Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>arcesia.retro is now online</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3734" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|''Harry''
|''404.retro''
|''ns.404.retro''
|''100.96.18.254''
|No DNS server on the member side yet.
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|''Cursed''
|''-''
|''-''
|''172.23.0.69''
|''Future CGHMN Mail Server''
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>56525602cd9bb0a39df74d21aa54ce1575967010</sha1>
  </revision>
  <revision>
    <id>234</id>
    <parentid>233</parentid>
    <timestamp>2025-06-27T06:41:19Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <minor/>
    <comment>404.retro is now online</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3683" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|''Cursed''
|''-''
|''-''
|''172.23.0.69''
|''Future CGHMN Mail Server''
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>4a260d7256f9d75d2896677d3bc3a9b02aa1cf20</sha1>
  </revision>
  <revision>
    <id>238</id>
    <parentid>234</parentid>
    <timestamp>2025-07-03T00:38:43Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3863" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|''Cursed''
|''-''
|''-''
|''172.23.0.69''
|''Future CGHMN Mail Server''
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>ec062330edb514a7c3a48e75418c009416760958</sha1>
  </revision>
  <revision>
    <id>239</id>
    <parentid>238</parentid>
    <timestamp>2025-07-11T01:27:13Z</timestamp>
    <contributor>
      <username>Gothpanda</username>
      <id>12</id>
    </contributor>
    <comment>Adding GothPanda to delegated domains and proxmox server</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4015" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|''Cursed''
|''-''
|''-''
|''172.23.0.69''
|''Future CGHMN Mail Server''
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>10440cb798bc0735991729150c27b242f96a4421</sha1>
  </revision>
  <revision>
    <id>249</id>
    <parentid>239</parentid>
    <timestamp>2025-07-13T19:38:26Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Add AskMe to the list of member delegated domains</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4080" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|hugh.loganius.retro
|100.96.9.100
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|''Cursed''
|''-''
|''-''
|''172.23.0.69''
|''Future CGHMN Mail Server''
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>d55c08adc55a8d5599dba978a688413f9f3f5e67</sha1>
  </revision>
</page>
<page arvcontinue="20250606090135|208">
  <title>AIM Clients</title>
  <ns>0</ns>
  <id>90</id>
  <revision>
    <id>209</id>
    <parentid>206</parentid>
    <timestamp>2025-06-10T02:46:56Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4357" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Windows testing is done on a Windows XP (32-bit) virtual machine with all updates applied  

Mac testing is done on OS X 10.6.8 via Proxmox 

Linux testing is done on Ubuntu 5.04 (32-bit) via Proxmox but may be augmented in future with different distros 

'''All testing was performed on [[Compu-Global-Hyper-Mega-Net|CGHMN]] to simplify packet captures. IP addresses do not reflect the ones used by regular RAS clients''' 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But should give users a general direction for further testing

Submissions are also welcome. Please feel free to email me or send me a message on Mastodon

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
Adium X 1.0.6 (x86) works! (PPC untested but presumed working)

Adium 1.3.10 (x86) works! (PPC untested but presumed working)

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

iChat on OS X Leopard (PPC or x86 unspecified) works!

AIM for OS 9 (PPC) works!

=== Linux ===
GAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed]

TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some reason?

== TESTED '''NOT''' WORKING ==


'''Windows'''

Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

'''Mac'''

Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


'''Linux'''

Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>1d3481114f73d91e8d888c0ccfd181927d64fd9f</sha1>
  </revision>
  <revision>
    <id>210</id>
    <parentid>209</parentid>
    <timestamp>2025-06-10T02:52:25Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4670" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Windows testing is done on a Windows XP (32-bit) virtual machine with all updates applied  

Mac testing is done on OS X 10.6.8 via Proxmox 

Linux testing is done on Ubuntu 5.04 (32-bit) via Proxmox but may be augmented in future with different distros 

'''All testing was performed on [[Compu-Global-Hyper-Mega-Net|CGHMN]] to simplify packet captures. IP addresses do not reflect the ones used by regular RAS clients''' 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But should give users a general direction for further testing

Submissions are also welcome. Please feel free to email me or send me a message on Mastodon

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
Adium X 1.0.6 (x86) works! (PPC untested but presumed working)

Adium 1.3.10 (x86) works! (PPC untested but presumed working)

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

iChat on OS X Leopard (PPC or x86 unspecified) works!

AIM for OS 9 (PPC) works!

=== Linux ===
GAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed]

TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some reason?

== TESTED '''NOT''' WORKING ==

=== Windows ===
Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== Mac ===
Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== Linux ===
Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== AmigaOS/MorphOS ===
nAIM 0.11.8.3.1 for AmigaOS - Also connects to its own TOC server '''(toc.n.ml.org)''' (DNS patched already previously for testing) but fails to connect similar to Linux client. Client did not produce any log files. [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>4a566f7c4766bbb9fd05cbb5b216c5461ec84b19</sha1>
  </revision>
  <revision>
    <id>211</id>
    <parentid>210</parentid>
    <timestamp>2025-06-10T04:14:02Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4862" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Windows testing is done on a Windows XP (32-bit) virtual machine with all updates applied  

Mac testing is done on OS X 10.6.8 via Proxmox 

Linux testing is done on Ubuntu 5.04 (32-bit) via Proxmox but may be augmented in future with different distros 

'''All testing was performed on [[Compu-Global-Hyper-Mega-Net|CGHMN]] to simplify packet captures. IP addresses do not reflect the ones used by regular RAS clients''' 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But should give users a general direction for further testing

Submissions are also welcome. Please feel free to email me or send me a message on Mastodon

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
Adium X 1.0.6 (x86) works! (PPC untested but presumed working)

Adium 1.3.10 (x86) works! (PPC untested but presumed working)

iChat 3.1.9 on OS X 10.4.11 (Tiger) PPC works!

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

iChat on OS X Leopard (PPC or x86 unspecified) works!

AIM for OS 9 (PPC) works!

=== Linux ===
GAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed]

TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some reason?

== TESTED '''NOT''' WORKING ==

=== Windows ===
Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== Mac ===
Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

AIM 4.7 on MacOS 9.2.2 - Complains about incorrect Username/Password. [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== Linux ===
Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== AmigaOS/MorphOS ===
nAIM 0.11.8.3.1 for AmigaOS - Also connects to its own TOC server '''(toc.n.ml.org)''' (DNS patched already previously for testing) but fails to connect similar to Linux client. Client did not produce any log files. [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>3a15a415cc1ad6243f6f8dc942697d297d32c473</sha1>
  </revision>
  <revision>
    <id>212</id>
    <parentid>211</parentid>
    <timestamp>2025-06-10T04:27:00Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4722" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Windows testing is done on a Windows XP (32-bit) virtual machine with all updates applied  

Mac testing is done on OS X 10.6.8 via Proxmox 

Linux testing is done on Ubuntu 5.04 (32-bit) via Proxmox but may be augmented in future with different distros 

'''All testing was performed on [[Compu-Global-Hyper-Mega-Net|CGHMN]] to simplify packet captures. IP addresses do not reflect the ones used by regular RAS clients''' 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But should give users a general direction for further testing

Submissions are also welcome. Please feel free to email me or send me a message on Mastodon

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
Adium X 1.0.6 (x86) works! (PPC untested but presumed working)

Adium 1.3.10 (x86) works! (PPC untested but presumed working)

iChat 3.1.9 on OS X 10.4.11 (Tiger) PPC works!

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

iChat on OS X Leopard (PPC or x86 unspecified) works!

AIM 4.7 for OS 9 (PPC) works!

=== Linux ===
GAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed]

TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some reason?

== TESTED '''NOT''' WORKING ==

=== Windows ===
Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== Mac ===
Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== Linux ===
Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== AmigaOS/MorphOS ===
nAIM 0.11.8.3.1 for AmigaOS - Also connects to its own TOC server '''(toc.n.ml.org)''' (DNS patched already previously for testing) but fails to connect similar to Linux client. Client did not produce any log files. [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>4b21299dabca897850c9e94006db68ececdf7c9d</sha1>
  </revision>
  <revision>
    <id>213</id>
    <parentid>212</parentid>
    <timestamp>2025-06-10T21:16:50Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4873" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Windows testing is done on a Windows XP (32-bit) virtual machine with all updates applied  

Mac testing is done on OS X 10.6.8 via Proxmox 

Linux testing is done on Ubuntu 5.04 (32-bit) via Proxmox but may be augmented in future with different distros 

'''All testing was performed on [[Compu-Global-Hyper-Mega-Net|CGHMN]] to simplify packet captures. IP addresses do not reflect the ones used by regular RAS clients''' 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But should give users a general direction for further testing

Submissions are also welcome. Please feel free to email me or send me a message on Mastodon

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
Adium X 1.0.6 (x86) works! (PPC untested but presumed working)

Adium 1.3.10 (x86) works! (PPC untested but presumed working)

iChat 3.1.9 on OS X 10.4.11 (Tiger) PPC works!

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

iChat on OS X Leopard (PPC or x86 unspecified) works!

AIM 4.7 for OS 9 (PPC) works!

=== Linux ===
GAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed]

TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some reason?

== TESTED '''NOT''' WORKING ==

=== Windows ===
Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== Mac ===
Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== Linux ===
Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== AmigaOS/MorphOS ===
nAIM 0.11.8.3.1 for AmigaOS - Also connects to its own TOC server '''(toc.n.ml.org)''' (DNS patched already previously for testing) but fails to connect similar to Linux client. Client did not produce any log files. [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

AmiAIM 0.11 for AmigaOS. Fails to connect, invalid username/password error. [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>f3865ad6f4919baee5126278f39e7a55ec21f318</sha1>
  </revision>
  <revision>
    <id>235</id>
    <parentid>213</parentid>
    <timestamp>2025-06-27T22:43:42Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5334" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Windows testing is done on a Windows XP (32-bit) virtual machine with all updates applied  

Mac testing is done on OS X 10.6.8 via Proxmox 

Linux testing is done on Ubuntu 5.04 (32-bit) via Proxmox but may be augmented in future with different distros 

'''All testing was performed on [[Compu-Global-Hyper-Mega-Net|CGHMN]] to simplify packet captures. IP addresses do not reflect the ones used by regular RAS clients but CGHMN is connected to ChivaNet/RAS''' 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But should give users a general direction for further testing

Submissions are also welcome. Please feel free to email me or send me a message on Mastodon

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s. AIM 1.7 refuses to install (requires Win95) but may also work under 3.11 with some tweaking (untested)

=== Mac ===
Adium X 1.0.6 (x86) works! (PPC untested but presumed working)

Adium 1.3.10 (x86) works! (PPC untested but presumed working)

iChat 3.1.9 on OS X 10.4.11 (Tiger) PPC works!

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

iChat on OS X Leopard (PPC or x86 unspecified) works!

AIM 4.7 for OS 9 (PPC) works!

=== Linux ===
GAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed]

TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some reason?

== TESTED '''NOT''' WORKING ==

=== Windows ===
Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== Mac ===
Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

AIM 2.1.302 - Queries '''clienturls.aol.com AND aoldiag.aol.com''' (fixed). Attempts to connect over HTTPS. Fails due to no SSL support currently -  [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

AIM 2.2.439 - Queries '''kdc.uas.aol.com''' (fixed) Attempts to connect over HTTPS. Fails due to no SSL support currently -  [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== Linux ===
Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== AmigaOS/MorphOS ===
nAIM 0.11.8.3.1 for AmigaOS - Also connects to its own TOC server '''(toc.n.ml.org)''' (DNS patched already previously for testing) but fails to connect similar to Linux client. Client did not produce any log files. [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

AmiAIM 0.11 for AmigaOS. Fails to connect, invalid username/password error. [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>c72115651784a1ad913dd63421651da24653bc38</sha1>
  </revision>
  <revision>
    <id>236</id>
    <parentid>235</parentid>
    <timestamp>2025-06-28T04:11:47Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5230" xml:space="preserve">This is just a scratch page for me to send the Retro AIM Server project on supported 3rd party AIM clients I've tested

Windows testing is done on a Windows XP (32-bit) virtual machine with all updates applied  

Mac testing is done on OS X 10.6.8 via Proxmox 

Linux testing is done on Ubuntu 5.04 (32-bit) via Proxmox but may be augmented in future with different distros 

'''All testing was performed on [[Compu-Global-Hyper-Mega-Net|CGHMN]] to simplify packet captures. IP addresses do not reflect the ones used by regular RAS clients but CGHMN is connected to ChivaNet/RAS''' 

This test isn't likely to be 100% coverage because I'm not going to test *every build* of every client. But should give users a general direction for further testing

Submissions are also welcome. Please feel free to email me or send me a message on Mastodon

== TESTED WORKING ==

=== Windows ===
Regular AIM. Pretty much all of these up to 6.1 (at time of writing) are tested and working. 6.1 should work on everything from Windows 9x/NT 4.0 through to Windows 11

AIM 1.5 also works on Windows 3.11 with Win32s

=== Mac ===
Adium X 1.0.6 (x86) works! (PPC untested but presumed working)

Adium 1.3.10 (x86) works! (PPC untested but presumed working)

iChat 3.1.9 on OS X 10.4.11 (Tiger) PPC works!

iChat 5.0.3 on OS X 10.6.8 (Snow Leopard) x86 works!

iChat on OS X Leopard (PPC or x86 unspecified) works!

AIM 4.7 for OS 9 (PPC) works!

=== Linux ===
GAIM 1.1.4 (Ubuntu 5.04) works. Though users will show as offline to other client(s) for several minutes. [https://github.com/mk6i/retro-aim-server/issues/123#issuecomment-2933138905 Bug filed]

TiK 0.90 (Ubuntu 5.04) works! Though needs to be run as root for some reason?

== TESTED '''NOT''' WORKING ==

=== Windows ===
Miranda 0.10.80 - Queries '''slogin.oscar.aol.com''' (fixed) but fails to connect. No errors printed by the client. Client also corrupts its database file if exited and relaunched - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== Mac ===
Adium 1.4.5 - Queries '''api.screenname.aol.com''' (fixed) and attempts to connect over HTTPS. Fails due to no SSL support currently - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

AIM 2.1.302 - Queries '''clienturls.aol.com AND aoldiag.aol.com''' (fixed). Attempts to connect over HTTPS. Fails due to no SSL support currently -  [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

AIM 2.2.439 - Queries '''kdc.uas.aol.com''' (fixed) Attempts to connect over HTTPS. Fails due to no SSL support currently -  [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== Linux ===
Ayttm 0.4.6-26 - Fails to connect to '''toc.oscar.aol.com''' (fixed) then returns 400 bad request from Nginx(?) - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Centreicq 4.13.0 - I have no goddamn idea how to use this client. But it seems to do...something? then eventually just shows '''[aim] disconnected''' - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

Kopete 0.10 - Attempts to connect but never completes. No errors reported from client - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

naim 0.11.7.2 - '''Seems to connect to its own TOC server toc.n.ml.org (???)''' (fixed) but fails to connect. Client logging enabled but did not produce any log files - [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

=== AmigaOS/MorphOS ===
nAIM 0.11.8.3.1 for AmigaOS - Also connects to its own TOC server '''(toc.n.ml.org)''' (DNS patched already previously for testing) but fails to connect similar to Linux client. Client did not produce any log files. [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]

AmiAIM 0.11 for AmigaOS. Fails to connect, invalid username/password error. [https://cursedsilicon.net/aim-packet-dumps/ Packet dump available here]


== UNTESTED ==


Adium X 0.89.1 - Fails to launch on OS X 10.6.8 (x86)

iChat v??? on OS X 10.7 (Lion) was the final client revision is currently untested as I cannot get it to successfully boot under Proxmox

Finch - Seems to be a plugin for Pidgin(?) to enable text mode chat instead of using a GUI?

Instantbird - Originally a Pidgin plugin. Later became its own stand-alone client. Development halted in 2013(?) with download servers unavailable. Downloaded final v1.5 via 3rd party FTP server but was unable to launch due to missing dependencies on Ubuntu 5.04

Jitsi - Cannot find old versions. Application seems to be more geared toward SIP and video conferencing?

Messages - Beta version was released for OS X '''''10.7''''' which I can't run under Proxmox currently

Quiet Internet Pager - Seems like possible malware? Judging by the quality of its Wikipedia page. Final version also was for PDA's instead of Windows(???)

TNT - Probably works? Last updated in 2006 and claims to support the "TOC2 protocol" (OSCAR?). But it's an '''''Emacs''''' client. I don't know how to use Emacs, let alone add AIM to it

VSide. Looks like a weird...SecondLife knockoff? Development halted in 2018 but it was never a messaging client. Just had AIM support attached to it</text>
    <sha1>bae16ccc28c089dec507178a7ab050311d81f49e</sha1>
  </revision>
</page>
<page arvcontinue="20250606090135|208">
  <title>How to Get Connected</title>
  <ns>0</ns>
  <id>82</id>
  <revision>
    <id>218</id>
    <parentid>194</parentid>
    <timestamp>2025-06-24T07:48:26Z</timestamp>
    <contributor>
      <username>Theothertom</username>
      <id>11</id>
    </contributor>
    <minor/>
    <comment>Add link to services page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11323" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
This is a quick and dirty "how do I get on CGHMN" 

'''Since the service is in "closed beta" these steps are a bit vague and manual. But over time as we figure out what works we'll add more connection methods and better documentation'''

=== Step 1: ===
[[Signup|'''Let us know you'd like to connect!''']] 

(We'll need information from you such as your Wireguard Pubkey to let you connect to the network)[[File:CGHMN.png|thumb|319x319px|Example CGHMN Router Setup using a GL-AR300M and basic network switch]]

=== Hardware requirements ===
To connect your retro machine(s) to the CGHMN, you'll need the following:
*'''An Ethernet connection on your retro device(s) of choice, with a TCP/IP (v4) stack for now! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works.'''

* '''Something with the ability to run Wireguard and forward IPv4 packets at the minimum and, for any non-IP packets, &lt;code&gt;gretap&lt;/code&gt; and &lt;code&gt;nftables&lt;/code&gt;. Personally we recommend something running OpenWRT, like the [https://www.gl-inet.com/products/gl-ar300m GL-AR300M] which we have successfully tested to work. We're currently working on a pre-built image for some select routers to make the setup easier for new members. A script to configure already existing OpenWRT instances can be found below.'''
* Alternatively, you can also run the CGHMN routing on any standard Linux box which has at least one Ethernet port and either a second one or WiFi for internet connectivity. &lt;s&gt;A basic script to set up a Linux machine as a router is posted below&lt;/s&gt; (TODO!).

* '''Optionally: A simple network switch, in case you want to add multiple machines to the network. You plug one end into the CGHMN Router box and then your clients can all access CGHMN. Super easy!'''

On the right is an example of what a CGHMN router setup could look like.

=== Get connected - With OpenWRT ===
If you chose to go with an OpenWRT compatible router or want to run OpenWRT on typical x86 hardware/in a VM, you can follow these steps to get yourself connected to the CGHMN:

# Update your OpenWRT install to the latest version to ensure all required packages are available and compatible.
# Download [https://raw.githubusercontent.com/jonasluehrig/cghmn-get-connected/refs/heads/main/openwrt/setup-cghmn.sh this script from GitHub] to your OpenWRT router: &lt;code&gt;wget https://cghmn.snep.zip/connect.sh&lt;/code&gt;
# Run the following commands on the router:
## &lt;code&gt;ash setup-cghmn.sh install-pkgs&lt;/code&gt;
## &lt;code&gt;ash setup-cghmn.sh init&lt;/code&gt;
## You will be asked what network port you'd like to use for the Retro LAN. This is where you will plug in your retro machines to be part of the CGHMN. Choose a port that is not assigned to any OpenWRT interface like '''lan''' or '''wan''' or which not already part of a bridge and enter the Linux interface name, e.g. &lt;code&gt;eth1&lt;/code&gt;, then press &lt;code&gt;[Enter]&lt;/code&gt; to continue. If your router only has two ports and you're using one for WAN, then you first have to [https://openwrt.org/docs/guide-user/luci/luci.secure#allow_access_from_internet enable the web UI and SSH access via the '''wan''' OpenWRT interface], remove the entire '''lan''' OpenWRT interface to free the network port and continue the setup over the IP address your router got on its WAN side. If you only have a single Ethernet port, you're running on a router setup we can't really recommend, however you can configure VLANs and use a managed switch to both get a WAN DHCP address for internet access and have a separate VLAN for the Retro LAN bridge over a single port. This is commonly referred to as "[[wikipedia:Router_on_a_stick|router on a stick]]". Just enter the VLAN interface name here if you choose to go that route.
# Now you will be given some information on the console, including a Wireguard public key. Send one of the CGHMN admins (currently CursedSilicon and Snep) that key so we can add your router to our Wireguard server. If you cannot copy-paste, for example, because you're on a VM VNC console, you can run &lt;code&gt;ash setup-cghmn.sh pubkey-qr&lt;/code&gt; to get a QR code printout of your public key, which can be scanned with a phone, tablet or software QR code parser to get the key as copy-pastable text.
# In return, you will receive a tunnel IPv4 address (&lt;code&gt;100.89.128.x/32&lt;/code&gt;) and a routed IPv4 subnet (&lt;code&gt;100.96.x.0/24&lt;/code&gt;) from us. These will be needed on the third and final step of the setup script:
## &lt;code&gt;ash setup-cghmn.sh set-tunnel-ip&lt;/code&gt;
# Once the script completed successfully, reboot the router to ensure all interfaces are up properly. After the reboot, your retro devices should receive an IP address in your routed IPv4 subnet on the Retro LAN port you chose above and be able to communicate with other machines on the CGHMN network.

=== Get Connected - Manually (Linux, Wireguard only, GRETAP follows shortly) ===
In case you want to setup a connection into the network manually, here are the required steps and information you should be needing:

* Generate a Wireguard private key and public key, this command writes a fresh Wireguard private key to &lt;code&gt;private-key&lt;/code&gt; and the corresponsing public key to &lt;code&gt;public-key&lt;/code&gt;:

 $ wg genkey | tee private-key | wg pubkey &gt; public-key

* NEVER share your private key, even with us! It should never be required outside of your own Wireguard setup!
* You will, however, need to share your public key with us. Send CursedSilicon or Snep on the Discord or via IRC a message including the public key and we'll add you to the tunnel.
* In return, you'll get two IP addresses from us: Your tunnel IP address, with which your router talks to our router, and a routed subnet, from which you can assign IPs to your own machines so they can talk to other CGHMN member devices on the network without NAT in the way.
* Next, you'll need to fill a Wireguard configuration file with the two IP addresses, like below:

 [Interface]
 PrivateKey = &lt;Your private key goes here&gt;
 Address = &lt;Your tunnel IP address goes here&gt;/32
 DNS = 100.89.128.0
 MTU = 1420
 
 [Peer]
 PublicKey = k/QiJIbMakMKgTCHVt8/D+8k4DzRVM6U33F3gMZfRUg=
 Endpoint = wg-admin.cursedsilicon.net:42070
 AllowedIPs = 172.23.0.0/16, 100.89.128.0/22, 100.96.0.0/13
 PersistentKeepalive = 15

* Save this file as &lt;code&gt;wg-cghmn.conf&lt;/code&gt;, for example.
* Then, run &lt;code&gt;wg-quick up ./wg-cghmn.conf&lt;/code&gt;, perhaps requiring &lt;code&gt;doas&lt;/code&gt;/&lt;code&gt;sudo&lt;/code&gt;, to bring the tunnel up and connect to the network!

This should bring whatever system you've set the tunnel up on onto the network and is now reachable for other members on the network, as long as the firewall on your device is congfigured accordingly, of course.

&lt;nowiki&gt;#&lt;/nowiki&gt;TODO: Add example of routed subnet configuration, perhaps on a different Wiki site

=== Get connected - Server Side, the Admins Guide ===
[[File:Example Configuration for new Wireguard Peer on Core Router.png|thumb|Example Configuration for new Wireguard Peer on Core Router]]
To get a member onto the network, they will send an admin of the project their randomly generated Wireguard key during the setup via the OpenWRT script. Here are the steps that admin will have to follow to get them up and running on the server side:

# Log in on the [https://router.core.cghmn:8443 Core Router] over an existing CGHMN network link
# Navigate to VPN -&gt; Wireguard -&gt; Peer Generator
# You will be asked to enter some data for the new peer, enter the following: 
## '''Instance:''' &lt;code&gt;WG_Member&lt;/code&gt;   
## '''Endpoint:''' &lt;code&gt;wg-admin.cursedsilicon.net:42070&lt;/code&gt;
## '''Name:''' &lt;code&gt;member.''&lt;Nickname of the new member&gt;''&lt;/code&gt;
## '''Public Key:''' &lt;code&gt;''&lt;their Wireguard public key they've sent over&gt;''&lt;/code&gt;
## '''Private Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Address:''' ''&lt;code&gt;&lt;Next highest IP from 100.89.128.0/22, this is their tunnel IP and is auto-filled&gt;&lt;/code&gt;''
## '''Pre-Shared Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Allowed IPs:''' &lt;code&gt;''&lt;the same as Address&gt;'', ''&lt;their routed subnet, [[How to Get Connected#But wait, what even is their routed subnet?|see below]]&gt;''&lt;/code&gt;
## '''Keepalive interval:''' ''&lt;code&gt;&lt;blank&gt;&lt;/code&gt;''
## '''DNS Servers:''' &lt;code&gt;''&lt;default value&gt;''&lt;/code&gt;
# Hit the "Store and generate next" button
# Navigate to VPN -&gt; Wireguard -&gt; Instances
# Hit the "Apply" button
# Do '''either one''' '''(not both!)''' of these steps, depending on if you can SSH into the GRETAP endpoint container:
## SSH into the CGHMN Proxmox Server and enter the command &lt;code&gt;pct enter 10403&lt;/code&gt;
## SSH directly into the GRETAP endpoint (formerly VXLAN endpoint) container with &lt;code&gt;ssh root@172.23.4.103&lt;/code&gt;
# From there, run the following command: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh &lt;member-tunnel-ip&gt; &lt;member-name&gt;&lt;/code&gt; where you replace &lt;code&gt;&lt;member-tunnel-ip&gt;&lt;/code&gt; with the IP tunnel address of the member as it was set above in the '''Address''' field, without the &lt;code&gt;/32&lt;/code&gt; CIDR subnet mask, and replace the &lt;code&gt;&lt;member-name&gt;&lt;/code&gt; with the same value you've entered above in the '''Name''' field. For example, like this: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh 100.89.128.6 member.snep.test&lt;/code&gt; This will create a GRETAP (and for legacy purposes, a VXLAN) interface and bring them up automagically. ''Ignore the fact it still says "VXLAN" everywhere, it does both.''
# Now you can send the member their Wireguard Tunnel IP and their routed subnet over and they can finish their client-side setup according to the mini-tutorial above.
# Rember to add the member and their tunnel and subnet IPs to the [[CGHMN-IP-Allocations|IP allocations page]] :)

==== But wait, what even ''is'' their routed subnet? ====
Each members routed subnet comes per default from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IPv4 block and has a &lt;code&gt;/24&lt;/code&gt; mask. This subnet is their "Retro LAN", to which all their retro computers are hooked into via the router of their choosing. By default, NAT is enabled on the routers, so it wouldn't make a difference which subnet is used on the remote end for the retro machines. However, if someone wants to host servers in the CGHMN and doesn't want to do port forwading, they can disable NAT and let other membres directly connect to their machines via this routed subnet.

To get the routed subnet of a member, take the number from the last octet of the Wireguard tunnel IP of a member, say &lt;code&gt;100.89.128.'''6'''&lt;/code&gt;, and put it into the third octet of the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IP block and replace the &lt;code&gt;/13&lt;/code&gt; with &lt;code&gt;/24&lt;/code&gt;, so you get &lt;code&gt;100.96.'''6'''.0/24&lt;/code&gt;. That is their routed subnet, simple as that!

=== After you get connected ===
There are a few optional things you might want to do.

==== Network mailing list ====
There is a mailing list you can subscribe to if you want to be notified about things that may affect CGHMN or core services. You can subscribe to the list here: https://berwick-upon-tweed.cobaltqu.be/postorius/lists/cghmn-announce.lists.cobaltqu.be/.


If you need to post to the list, you will need to subscribe before you can be added to the list of poster.

==== Explore things available on the network ====
There is a collection of [[services people are running]] - things like email/hosting/chat/search/etc.</text>
    <sha1>668956e82842ca491f334f9b6511b8aa5acf4e2e</sha1>
  </revision>
</page>
<page arvcontinue="20250606090135|208">
  <title>Services people are running</title>
  <ns>0</ns>
  <id>91</id>
  <revision>
    <id>219</id>
    <timestamp>2025-06-24T08:32:24Z</timestamp>
    <contributor>
      <username>Theothertom</username>
      <id>11</id>
    </contributor>
    <comment>Created page with "This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!  == Chat ==  === AIM === CGHMN connects to Chivanet's AIM service. To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.  === IRC === Available on irc.cghmn.retro (no TLS), and bridged onto the regular internet and Discord..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1556" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service. To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
Available on irc.cghmn.retro (no TLS), and bridged onto the regular internet and Discord. 

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN mail ===
(I forgot the URL). This is run by the core team.

Webmail: available - targets IE5 on Windows 3.1 as a minimum.

IMAP: ???

POP: ???

== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/Mailing lists
|}
How to sign up: message theothertom on IRC.

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

== Search ==

=== Oohay ===
Available on oohay.retro.

Indexing approach: Must submit pages for indexing</text>
    <sha1>7b257de323b8b54870c55f187943e1e2797f763d</sha1>
  </revision>
  <revision>
    <id>220</id>
    <parentid>219</parentid>
    <timestamp>2025-06-24T08:37:00Z</timestamp>
    <contributor>
      <username>Theothertom</username>
      <id>11</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1598" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service. To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
Available on irc.cghmn.retro (no TLS), and bridged onto the regular internet and Discord. 

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN mail ===
(I forgot the URL). This is run by the core team.

Webmail: available - targets IE5 on Windows 3.1 as a minimum.

IMAP: ???

POP: ???

== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/Mailing lists
|}
How to sign up: message theothertom on IRC.

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Oohay ===
Available on oohay.retro.

Indexing approach: Must submit pages for indexing</text>
    <sha1>e0b5b29b20070317729da72ef5b59a21778c0bcc</sha1>
  </revision>
  <revision>
    <id>221</id>
    <parentid>220</parentid>
    <timestamp>2025-06-24T08:37:31Z</timestamp>
    <contributor>
      <username>Theothertom</username>
      <id>11</id>
    </contributor>
    <comment>/* Theotherhost */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1602" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service. To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
Available on irc.cghmn.retro (no TLS), and bridged onto the regular internet and Discord. 

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN mail ===
(I forgot the URL). This is run by the core team.

Webmail: available - targets IE5 on Windows 3.1 as a minimum.

IMAP: ???

POP: ???

== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
How to sign up: message theothertom on IRC.

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Oohay ===
Available on oohay.retro.

Indexing approach: Must submit pages for indexing</text>
    <sha1>087a55cb1df23c22428e9614cdb399a146150e0c</sha1>
  </revision>
  <revision>
    <id>222</id>
    <parentid>221</parentid>
    <timestamp>2025-06-24T08:44:04Z</timestamp>
    <contributor>
      <username>Theothertom</username>
      <id>11</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1696" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service. To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
Available on irc.cghmn.retro (no TLS), and bridged onto the regular internet and Discord. 

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN mail ===
(I forgot the URL). This is run by the core team.

Webmail: available - targets IE5 on Windows 3.1 as a minimum.

IMAP: ???

POP: ???

== Game servers ==
This feels like a category where adding TODOs is particularly encouraged?

== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
How to sign up: message theothertom on IRC.

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Oohay ===
Available on oohay.retro.

Indexing approach: Must submit pages for indexing</text>
    <sha1>c9ce0b7d633d6b9b4459fc90111ae4d88044dee4</sha1>
  </revision>
  <revision>
    <id>223</id>
    <parentid>222</parentid>
    <timestamp>2025-06-24T09:30:38Z</timestamp>
    <contributor>
      <username>Theothertom</username>
      <id>11</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1749" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service. To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
Available on irc.cghmn.retro (no TLS), and bridged onto the regular internet and Discord. 

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN mail ===
cghmn-mail.retro. This is run by cursedsilicon.

Webmail: available - targets IE5 on Windows 3.1 as a minimum.

IMAP: ???

POP: ???

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
This feels like a category where adding TODOs is particularly encouraged?

== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
How to sign up: message theothertom on IRC.

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Oohay ===
Available on oohay.retro.

Indexing approach: Must submit pages for indexing</text>
    <sha1>7138675518c3897ddd9ec4f58bd814ebc420d016</sha1>
  </revision>
  <revision>
    <id>229</id>
    <parentid>223</parentid>
    <timestamp>2025-06-24T22:37:38Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Add a websites section and add my game servers.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2538" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service. To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
Available on irc.cghmn.retro (no TLS), and bridged onto the regular internet and Discord. 

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN mail ===
cghmn-mail.retro. This is run by cursedsilicon.

Webmail: available - targets IE5 on Windows 3.1 as a minimum.

IMAP: ???

POP: ???

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.1
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|}
You must at least specify either the IP or the hostname, otherwise people won't be able to connect to your server.

This feels like a category where adding TODOs is particularly encouraged?

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or http://live.loganius.retro:81/&lt;/nowiki&gt;
|}
IP/Hostname = What should people type into their browser to reach your site.

== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
How to sign up: message theothertom on IRC.

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Oohay ===
Available on oohay.retro.

Indexing approach: Must submit pages for indexing</text>
    <sha1>43282be573075329ea78d554983d797abbe00b8b</sha1>
  </revision>
  <revision>
    <id>231</id>
    <parentid>229</parentid>
    <timestamp>2025-06-25T22:04:12Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3484" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
Available on irc.cghmn.retro (no TLS), and bridged onto the regular internet and Discord. 

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: Both should connect as "insecure/plaintext" modes. I'm too lazy to set up SSL encryption yet'''

How to sign up: @cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.1
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or http://live.loganius.retro:81/&lt;/nowiki&gt;
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Oohay ===
Available on oohay.retro.

'''Indexing approach: Must submit pages for indexing'''</text>
    <sha1>429d0fba4830fd3a2a87650c4339fefa4ba1cab8</sha1>
  </revision>
  <revision>
    <id>237</id>
    <parentid>231</parentid>
    <timestamp>2025-07-01T01:18:39Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3620" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
Available on irc.cghmn.retro (no TLS), and bridged onto the regular internet and Discord. 

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: Both should connect as "insecure/plaintext" modes. I'm too lazy to set up SSL encryption yet'''

How to sign up: @cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.1
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or http://live.loganius.retro:81/&lt;/nowiki&gt;
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Oohay ===
Available on '''oohay.retro'''

'''Must submit pages for indexing'''

=== Google Search Appliance ===
Available on '''google.retro'''

'''Submit domains for indexing to CursedSilicon. Crawling takes about 15 minutes'''</text>
    <sha1>f51a5507993ee8dd522c15c09a85937ea305a16f</sha1>
  </revision>
  <revision>
    <id>240</id>
    <parentid>237</parentid>
    <timestamp>2025-07-13T01:33:46Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3677" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
Available on irc.cghmn.retro (no TLS), and bridged onto the regular internet and Discord. 

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: SSL is ''enabled'' but is not widely tested. Your mileage may vary. If you experience issues, just use insecure/plaintext modes for simplicity'''

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.1
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or http://live.loganius.retro:81/&lt;/nowiki&gt;
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Oohay ===
Available on '''oohay.retro'''

'''Must submit pages for indexing'''

=== Google Search Appliance ===
Available on '''google.retro'''

'''Submit domains for indexing to CursedSilicon. Crawling takes about 15 minutes'''</text>
    <sha1>8726c3555db85961625cb72c0721c21e1c365d80</sha1>
  </revision>
  <revision>
    <id>241</id>
    <parentid>240</parentid>
    <timestamp>2025-07-13T01:35:25Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3851" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
Available on irc.cghmn.retro (no TLS), and bridged onto the regular internet and Discord. 

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: SSL is ''enabled'' but is not widely tested. Your mileage may vary. If you experience issues, just use insecure/plaintext modes for simplicity'''

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.1
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or http://live.loganius.retro:81/&lt;/nowiki&gt;
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Oohay ===
Available on '''oohay.retro'''

'''Must submit pages for indexing'''

=== Google Search Appliance ===
Available on '''google.retro'''

'''Submit domains for indexing to CursedSilicon. Crawling takes about 15 minutes'''

=== Pandia Search ===
Available on '''''www.chivanet''''' (no TLD but WWW is required!)

Has both a web and CGHMN version

'''Message Serena to have your website indexed'''</text>
    <sha1>22ecb1b09c9938d14e732eaa217b4ade96f95b58</sha1>
  </revision>
  <revision>
    <id>242</id>
    <parentid>241</parentid>
    <timestamp>2025-07-13T02:32:00Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3844" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
Available on irc.cghmn.retro (no TLS), and bridged onto the regular internet and Discord. 

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: SSL is ''enabled'' but is not widely tested. Your mileage may vary. If you experience issues, just use insecure/plaintext modes for simplicity'''

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.1
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or http://live.loganius.retro:81/&lt;/nowiki&gt;
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Oohay ===
Available on '''oohay.retro'''

'''Must submit pages for indexing'''

=== Google Search Appliance ===
Available on '''google.retro'''

'''Submit domains for indexing to CursedSilicon. Crawling takes about 15 minutes'''

=== Pandia Search ===
Available on '''''www.chivanet''''' (no TLD but WWW is required!)

Has both a web and CGHMN version

'''Sites can be added via the Pandia UI'''</text>
    <sha1>5af826413dc11b0cf13c548187c30c081ccb8b93</sha1>
  </revision>
  <revision>
    <id>243</id>
    <parentid>242</parentid>
    <timestamp>2025-07-13T03:00:46Z</timestamp>
    <contributor>
      <username>Snw</username>
      <id>13</id>
    </contributor>
    <comment>/* Pandia Search */ elucidate the web/CGHMN feature in Pandia</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3920" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
Available on irc.cghmn.retro (no TLS), and bridged onto the regular internet and Discord. 

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: SSL is ''enabled'' but is not widely tested. Your mileage may vary. If you experience issues, just use insecure/plaintext modes for simplicity'''

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.1
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or http://live.loganius.retro:81/&lt;/nowiki&gt;
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Oohay ===
Available on '''oohay.retro'''

'''Must submit pages for indexing'''

=== Google Search Appliance ===
Available on '''google.retro'''

'''Submit domains for indexing to CursedSilicon. Crawling takes about 15 minutes'''

=== Pandia Search ===
Available on '''''www.chivanet''''' (no TLD but WWW is required!)

Has both a web and CGHMN version (automatically selected by detecting the domain from which the user visits)

'''Sites can be added via the Pandia UI'''</text>
    <sha1>ef9d52e104fbafc04e945b58b43a1c8622eab98c</sha1>
  </revision>
  <revision>
    <id>244</id>
    <parentid>243</parentid>
    <timestamp>2025-07-13T03:57:19Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Add AskMe to and remove Oohay from the list of search engines.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4006" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
Available on irc.cghmn.retro (no TLS), and bridged onto the regular internet and Discord. 

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: SSL is ''enabled'' but is not widely tested. Your mileage may vary. If you experience issues, just use insecure/plaintext modes for simplicity'''

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.1
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or http://live.loganius.retro:81/&lt;/nowiki&gt;
|-
|Loganius
|askme.retro
|Windows Server 2003 R2
|IIS 6.0
|The AskMe Search Engine
|
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Google Search Appliance ===
Available on '''google.retro'''

'''Submit domains for indexing to CursedSilicon. Crawling takes about 15 minutes'''

=== Pandia Search ===
Available on '''''www.chivanet''''' (no TLD but WWW is required!)

Has both a web and CGHMN version (automatically selected by detecting the domain from which the user visits)

'''Sites can be added via the Pandia UI'''

=== AskMe ===
Available on '''askme.retro'''

'''Must submit pages for indexing'''</text>
    <sha1>d1d0b8da087aba98682b0306aae32f5b3ad8746d</sha1>
  </revision>
  <revision>
    <id>245</id>
    <parentid>244</parentid>
    <timestamp>2025-07-13T04:18:55Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Add Oohay to the list of websites</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4116" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
Available on irc.cghmn.retro (no TLS), and bridged onto the regular internet and Discord. 

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: SSL is ''enabled'' but is not widely tested. Your mileage may vary. If you experience issues, just use insecure/plaintext modes for simplicity'''

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.1
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or http://live.loganius.retro:81/&lt;/nowiki&gt;
|-
|Loganius
|askme.retro
|Windows Server 2003 R2
|IIS 6.0
|The AskMe Search Engine
|
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|-
|ch0ccyra1n
|oohay.retro
|Ubuntu Server
|Nginx
|A collection of services for Compu-Global-Hyper-Mega-Net
|
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Google Search Appliance ===
Available on '''google.retro'''

'''Submit domains for indexing to CursedSilicon. Crawling takes about 15 minutes'''

=== Pandia Search ===
Available on '''''www.chivanet''''' (no TLD but WWW is required!)

Has both a web and CGHMN version (automatically selected by detecting the domain from which the user visits)

'''Sites can be added via the Pandia UI'''

=== AskMe ===
Available on '''askme.retro'''

'''Must submit pages for indexing'''</text>
    <sha1>4e90b694dd2392585ab76337d2129755102fcc32</sha1>
  </revision>
  <revision>
    <id>246</id>
    <parentid>245</parentid>
    <timestamp>2025-07-13T04:30:51Z</timestamp>
    <contributor>
      <username>Ch0ccyra1n</username>
      <id>14</id>
    </contributor>
    <comment>Create table for IRC servers</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4213" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
{| class="wikitable"
|+
!Hostname
!Port (non-TLS)
!TLS?
!Notes
|-
|irc.cghmn.retro
|6667
|no
|Bridged onto the regular internet and Discord
|-
|irc.loganius.retro
|6667
|yes, at 6697
|
|}

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: SSL is ''enabled'' but is not widely tested. Your mileage may vary. If you experience issues, just use insecure/plaintext modes for simplicity'''

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.1
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or http://live.loganius.retro:81/&lt;/nowiki&gt;
|-
|Loganius
|askme.retro
|Windows Server 2003 R2
|IIS 6.0
|The AskMe Search Engine
|
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|-
|ch0ccyra1n
|oohay.retro
|Ubuntu Server
|Nginx
|A collection of services for Compu-Global-Hyper-Mega-Net
|
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Google Search Appliance ===
Available on '''google.retro'''

'''Submit domains for indexing to CursedSilicon. Crawling takes about 15 minutes'''

=== Pandia Search ===
Available on '''''www.chivanet''''' (no TLD but WWW is required!)

Has both a web and CGHMN version (automatically selected by detecting the domain from which the user visits)

'''Sites can be added via the Pandia UI'''

=== AskMe ===
Available on '''askme.retro'''

'''Must submit pages for indexing'''</text>
    <sha1>9063efb603c8bb89649131958bc154162d501bda</sha1>
  </revision>
  <revision>
    <id>247</id>
    <parentid>246</parentid>
    <timestamp>2025-07-13T04:32:32Z</timestamp>
    <contributor>
      <username>Ch0ccyra1n</username>
      <id>14</id>
    </contributor>
    <minor/>
    <comment>Add page to Compu-Global-Hyper-Mega-Net category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4254" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
{| class="wikitable"
|+
!Hostname
!Port (non-TLS)
!TLS?
!Notes
|-
|irc.cghmn.retro
|6667
|no
|Bridged onto the regular internet and Discord
|-
|irc.loganius.retro
|6667
|yes, at 6697
|
|}

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: SSL is ''enabled'' but is not widely tested. Your mileage may vary. If you experience issues, just use insecure/plaintext modes for simplicity'''

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.1
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or http://live.loganius.retro:81/&lt;/nowiki&gt;
|-
|Loganius
|askme.retro
|Windows Server 2003 R2
|IIS 6.0
|The AskMe Search Engine
|
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|-
|ch0ccyra1n
|oohay.retro
|Ubuntu Server
|Nginx
|A collection of services for Compu-Global-Hyper-Mega-Net
|
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Google Search Appliance ===
Available on '''google.retro'''

'''Submit domains for indexing to CursedSilicon. Crawling takes about 15 minutes'''

=== Pandia Search ===
Available on '''''www.chivanet''''' (no TLD but WWW is required!)

Has both a web and CGHMN version (automatically selected by detecting the domain from which the user visits)

'''Sites can be added via the Pandia UI'''

=== AskMe ===
Available on '''askme.retro'''

'''Must submit pages for indexing'''
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>71f4d1da8a277aed92e5795965dc4bb8e160919e</sha1>
  </revision>
  <revision>
    <id>255</id>
    <parentid>247</parentid>
    <timestamp>2025-07-15T18:18:04Z</timestamp>
    <contributor>
      <username>Snw</username>
      <id>13</id>
    </contributor>
    <comment>/* Game servers */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4382" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
{| class="wikitable"
|+
!Hostname
!Port (non-TLS)
!TLS?
!Notes
|-
|irc.cghmn.retro
|6667
|no
|Bridged onto the regular internet and Discord
|-
|irc.loganius.retro
|6667
|yes, at 6697
|
|}

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: SSL is ''enabled'' but is not widely tested. Your mileage may vary. If you experience issues, just use insecure/plaintext modes for simplicity'''

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.1
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|-
|Serena
|wow.chivanet
|100.96.13.13
|World of Warcraft 3.3.5a (Wrath of the Lich King)
|Linux
|Message Serena for an account
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or http://live.loganius.retro:81/&lt;/nowiki&gt;
|-
|Loganius
|askme.retro
|Windows Server 2003 R2
|IIS 6.0
|The AskMe Search Engine
|
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|-
|ch0ccyra1n
|oohay.retro
|Ubuntu Server
|Nginx
|A collection of services for Compu-Global-Hyper-Mega-Net
|
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Google Search Appliance ===
Available on '''google.retro'''

'''Submit domains for indexing to CursedSilicon. Crawling takes about 15 minutes'''

=== Pandia Search ===
Available on '''''www.chivanet''''' (no TLD but WWW is required!)

Has both a web and CGHMN version (automatically selected by detecting the domain from which the user visits)

'''Sites can be added via the Pandia UI'''

=== AskMe ===
Available on '''askme.retro'''

'''Must submit pages for indexing'''
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>f2638b09ba5a11fe32fc56569f05f5626e67083c</sha1>
  </revision>
  <revision>
    <id>256</id>
    <parentid>255</parentid>
    <timestamp>2025-07-22T05:41:30Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Update the info for the services I'm running</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4485" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
{| class="wikitable"
|+
!Hostname
!Port (non-TLS)
!TLS?
!Notes
|-
|irc.cghmn.retro
|6667
|no
|Bridged onto the regular internet and Discord
|-
|irc.loganius.retro
|6667
|yes, at 6697
|Must register your nick with NickServ before you can start talking. You'll need working email for this.
|}

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: SSL is ''enabled'' but is not widely tested. Your mileage may vary. If you experience issues, just use insecure/plaintext modes for simplicity'''

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.6
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|-
|Serena
|wow.chivanet
|100.96.13.13
|World of Warcraft 3.3.5a (Wrath of the Lich King)
|Linux
|Message Serena for an account
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or http://live.loganius.retro:81/&lt;/nowiki&gt;
|-
|Loganius
|askme.retro
|Windows Server 2003 R2
|IIS 6.0
|The AskMe Search Engine
|
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|-
|ch0ccyra1n
|oohay.retro
|Ubuntu Server
|Nginx
|A collection of services for Compu-Global-Hyper-Mega-Net
|
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Google Search Appliance ===
Available on '''google.retro'''

'''Submit domains for indexing to CursedSilicon. Crawling takes about 15 minutes'''

=== Pandia Search ===
Available on '''''www.chivanet''''' (no TLD but WWW is required!)

Has both a web and CGHMN version (automatically selected by detecting the domain from which the user visits)

'''Sites can be added via the Pandia UI'''

=== AskMe ===
Available on '''askme.retro'''

'''Must submit pages for indexing'''
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>f415fa4f505ca61c17abf89d18ec2a96c632b700</sha1>
  </revision>
</page>
<page arvcontinue="20250606090135|208">
  <title>User:Hadn69</title>
  <ns>2</ns>
  <id>92</id>
  <revision>
    <id>248</id>
    <timestamp>2025-07-13T05:05:32Z</timestamp>
    <contributor>
      <username>Hadn69</username>
      <id>15</id>
    </contributor>
    <comment>Created page with "This is a test of the page creation system. If you have received this message, please ignore it."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="96" xml:space="preserve">This is a test of the page creation system. If you have received this message, please ignore it.</text>
    <sha1>30da9815a403543541a0a512815de9b92449bcc2</sha1>
  </revision>
</page>
<page arvcontinue="20250606090135|208">
  <title>Netra T1</title>
  <ns>0</ns>
  <id>44</id>
  <revision>
    <id>250</id>
    <parentid>71</parentid>
    <timestamp>2025-07-15T10:55:21Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="515" xml:space="preserve">Along with its much larger brother the [[SunFire Enterprise 420R|Sunfire 420R]] the Netra T1 100 is one of the several pieces of Sun equipment in my collection

At this time I don't have much information to post about it. I have not powered any of the Sun equipment on to investigate it deeper

Also the face plate fell off. Though apparently that's common with the brittle plastic
[[File:Netra T1 (front).jpg|none|thumb|Netra T1 (front)]]
[[File:Netra T1 (Rear).jpg|alt=Netra T1 (Rear)|none|thumb|Netra T1 (Rear)]]</text>
    <sha1>abd33f6a4d3d3b8ef9e865b15f14c4192b9ff5f9</sha1>
  </revision>
</page>
<page arvcontinue="20250606090135|208">
  <title>Mac Mini G4</title>
  <ns>0</ns>
  <id>80</id>
  <revision>
    <id>251</id>
    <parentid>143</parentid>
    <timestamp>2025-07-15T10:58:26Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="496" xml:space="preserve">My iMac G3/350 "BlueBerry" died during the March 2025 Interim Computer Festival


So I bought a G4 1.5Ghz Mac Mini from [https://os9.shop some dude in Virginia] who sells refurbed ones running OS 9.2.2 of all things?


It's a maxed out Mac Mini G4 @ 1.5Ghz with 1GB of RAM and a 120GB mSATA SSD on an IDE adapter card


'''After disassembling it to remove its (cheap as hell) SSD the power button detached from the main system board. It needs to be replaced before the unit can reenter service'''</text>
    <sha1>70b6a0bd1c8a60c0754d95e500bc9d8eb44e1c5e</sha1>
  </revision>
</page>
<page arvcontinue="20250606090135|208">
  <title>Old Computers</title>
  <ns>0</ns>
  <id>2</id>
  <revision>
    <id>252</id>
    <parentid>142</parentid>
    <timestamp>2025-07-15T10:59:16Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1250" xml:space="preserve">As the title suggests, and indeed why you're here. '''''I have a lot of old computers'''''

This page serves as an index catalog of them for easy reference.

&lt;big&gt;'''NOTE: This list is non-exhaustive as I'm constantly picking up new weird old tech'''&lt;/big&gt;


=== Acer Inc ===
[[Acer EasyStore H340]]

=== Apple Computers Inc ===
[[Powermac G4]] "Mirror Drive Door" (MDD)

[[Powermac G5]] Quad

[[Mac Mini G4]]

[[Xserve G4]]

[[Xserve G5]]
=== Cobalt Networks ===
[[Cobalt Qube]]

[[Cobalt RaQ|Cobalt RaQ4]]

=== Dell Computers ===
[[PowerEdge 2500]]

[[OptiPlex GX1]]

[[Dell XPS Pro200N|XPS Pro200N]]

[[Dimension XPS D266]]

=== Digital Equipment Corporation ===
[[DEC AlphaServer 2100|DEC AlphaServer 2100 4/275]]

=== Hewlett Packard ===
[[HP MediaSmart EX495]]

[[HP KAYAK XA 6/400 MT]]

=== Silicon Graphics ===
[[SGI Octane]]

[[SGI Visual Workstation 320]]

=== Sun Microsystems ===
[[Netra X1]]

[[Netra T1]]

[[SunFire Enterprise 420R]] 

[[Ultra 10 Workstation]]

=== Whitebox/custom builds ===

[[Windows 98 PC|World's Fastest Windows 98 PC]]

[[Disc Ripper|Disc Ripper aka "Napster"]]

=== Miscellaneous (Anything not 'retro') ===
[[Framework 13]]

[[Main Desktop]]

[[Home Server]]

[[Hyve Zeus]]

[[Hyve Cygnus]]

[[Video Capture PC]]</text>
    <sha1>2f2e1ab2c2797b97a90d7d7a57109fb62223172b</sha1>
  </revision>
  <revision>
    <id>253</id>
    <parentid>252</parentid>
    <timestamp>2025-07-15T11:00:08Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1206" xml:space="preserve">As the title suggests, and indeed why you're here. '''''I have a lot of old computers'''''

This page serves as an index catalog of them for easy reference.

&lt;big&gt;'''NOTE: This list is non-exhaustive as I'm constantly picking up new weird old tech'''&lt;/big&gt;


=== Acer Inc ===
[[Acer EasyStore H340]]

=== Apple Computers Inc ===
[[Powermac G4]] "Mirror Drive Door" (MDD)

[[Powermac G5]] Quad

[[Mac Mini G4]]

[[Xserve G4]]

[[Xserve G5]]
=== Cobalt Networks ===
[[Cobalt Qube]]

[[Cobalt RaQ|Cobalt RaQ4]]

=== Dell Computers ===
[[PowerEdge 2500]]

[[Dell XPS Pro200N|XPS Pro200N]]

[[Dimension XPS D266]]

=== Digital Equipment Corporation ===
[[DEC AlphaServer 2100|DEC AlphaServer 2100 4/275]]

=== Hewlett Packard ===
[[HP MediaSmart EX495]]

=== Silicon Graphics ===
[[SGI Octane]]

[[SGI Visual Workstation 320]]

=== Sun Microsystems ===
[[Netra X1]]

[[Netra T1]]

[[SunFire Enterprise 420R]] 

[[Ultra 10 Workstation]]

=== Whitebox/custom builds ===

[[Windows 98 PC|World's Fastest Windows 98 PC]]

[[Disc Ripper|Disc Ripper aka "Napster"]]

=== Miscellaneous (Anything not 'retro') ===
[[Framework 13]]

[[Main Desktop]]

[[Home Server]]

[[Hyve Zeus]]

[[Hyve Cygnus]]

[[Video Capture PC]]</text>
    <sha1>9ecf1a95cc80464cc33be7641670e856848d1ee4</sha1>
  </revision>
</page>
<page arvcontinue="20250606090135|208">
  <title>Cobalt Qube 2</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>254</id>
    <parentid>8</parentid>
    <timestamp>2025-07-15T11:00:52Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2071" xml:space="preserve">The Cobalt Qube was the worlds first "Linux Appliance" designed and released by Cobalt Networks (later purchased by Sun Microsystems). Sold from 1998 to 2002 it features a modified Red Hat Linux operating system and a proprietary Web GUI for server management. 

The original Qube systems were equipped with MIPS RM5230 (150Mhz, Original Qube) or RM5231 (250Mhz, Qube 2) processors. These CPU's are similar to the RM5000 series in SGI's "Indy" workstations. 

Both the Qube 1 and 2 come with 16MB of RAM (2x8MB SIMM's) and an 8GB or 10GB 3.5 inch IDE hard disk as standard. 

Gateway also produced re-badged Cobalt Qube 2's which came in black and included a PCI Dial-Up modem. '''I do not have one of these so I cannot document its functionality or specifications'''

The original power supply can (and should) be replaced with a 45W USB-C power adapter. Bridging it requires a USB-C to 12V barrel connector and a Barrel to 3-pin DIN (Male) 5.5x 2.1mm cable

There is also a 40mm internal fan that should be replaced. Installing heatsinks on all internal chips is also recommended to prolong the lifespan of the device.


My Cobalt Qube 2 has been significantly modified since I purchased it from a user on eBay in late 2023. Some of the present modifications include

* RAM is maxed out to 256MB

* The original IDE hard disk has been replaced with 120GB SATA SSD using Startech SATA to IDE adapter. Due to the slow disk controller on the Cobalt Qube 2 (4MB/s at best) an SD card may be a more economical replacement
* The "BIOS" (or system bootstrap ROM) has been replaced with the "CoLo" bootloader. The original Cobalt firmware was hard-coded to launch a Linux kernel from an '''ext2 ''(not ext3 or ext4!)''''' partition on /dev/hda1


CoLo additionally allows connection to the unit via the RS232 serial port for system control after power on. The standard 115200,8,1 configuration will allow connection to the unit. Kernels can be downloaded and executed via TFTP via the CoLo interface


'''At this time the unit is functional, but not presently in operation'''</text>
    <sha1>210703817152a203528dc0b626815882596f0de4</sha1>
  </revision>
</page>
<page arvcontinue="20250606090135|208">
  <title>Dell XPS Pro200N</title>
  <ns>0</ns>
  <id>64</id>
  <revision>
    <id>257</id>
    <parentid>108</parentid>
    <timestamp>2025-08-05T00:59:57Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1211" xml:space="preserve">Recent pickup from a University of Washington (UW) auction. 

This unit is currently equipped with

- A Pentium Pro 200Mhz(!)

- 128MB of EDO memory (max may be higher? Dell only shipped up to 128MB in this unit)

- Two 120GB SSD's. One on each IDE channel (using Startech SATA to IDE adapters)

- Matrox Millennium II 8MB video card

- 3Com 3C950C-TX 10/100 network card

Currently it is installed with Windows 3.11 and "Stampede Linux" 0.90. Stampede is a Pentium processor optimized Linux distribution that derives from Slackware 7

Due to the distribution being end-of-lifed roughly 25 years ago it's likely to be replaced with a "Pentium Optimized Linux from Scratch" at a later date, pending purchase of a video card that contains an accelerated X server (the Matrox Millennium requires the "MGA" kernel driver and did not exist in 2.0/2.2 kernels according to research)


Images of this device also show several (unknown) expansion cards from what ever it was being used for originally. These have been removed after photographing

[[File:PXL 20250214 033500161.jpg|thumb|alt=XPS Pro 200N (front)|XPS Pro 200N (front)]]
[[File:PXL 20250214 033516741.jpg|thumb|alt=XPS Pro 200N (rear)|PS Pro 200N (rear)]]</text>
    <sha1>6e28f65d160130c27dbadb399cddfe5c524e0799</sha1>
  </revision>
</page>
<page arvcontinue="20250816031124|259">
  <title>CGHMN-IP-Allocations</title>
  <ns>0</ns>
  <id>77</id>
  <revision>
    <id>259</id>
    <parentid>249</parentid>
    <timestamp>2025-08-16T03:11:24Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Update IP allocations list</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4731" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|hugh.loganius.retro
|100.96.9.100
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|hugh.loganius.retro
|100.96.9.100
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|''Cursed''
|''-''
|''-''
|''172.23.0.69''
|''Future CGHMN Mail Server''
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>49ddec477bb762d8e05d47b294d22b57fafe1a5d</sha1>
  </revision>
  <revision>
    <id>260</id>
    <parentid>259</parentid>
    <timestamp>2025-08-16T03:13:17Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Update DNS server for loganius.retro</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4729" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|kirk.loganius.retro
|100.96.9.3
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|hugh.loganius.retro
|100.96.9.100
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|''Cursed''
|''-''
|''-''
|''172.23.0.69''
|''Future CGHMN Mail Server''
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>80e81b71b80739b3cbb1256d938b5b4f1004795f</sha1>
  </revision>
  <revision>
    <id>261</id>
    <parentid>260</parentid>
    <timestamp>2025-08-21T20:53:56Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Add my new Win2k ILS server</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4797" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|kirk.loganius.retro
|100.96.9.3
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|hugh.loganius.retro
|100.96.9.100
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|Cursed
|107
|cghmn-mail.retro
|172.23.0.69
|Mail Server
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|-
|Loganius
|109
|worf.loganius.retro
|172.23.0.55
|ILS Server (for MS NetMeeting)
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>fadabb10e16dcfe6a1c6f7a26cc15c9a933f07a7</sha1>
  </revision>
  <revision>
    <id>262</id>
    <parentid>261</parentid>
    <timestamp>2025-08-22T21:29:51Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <minor/>
    <comment>AskMe.retro also uses Kirk</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4795" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|kirk.loganius.retro
|100.96.9.3
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|kirk.loganius.retro
|100.96.9.3
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|Cursed
|107
|cghmn-mail.retro
|172.23.0.69
|Mail Server
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|-
|Loganius
|109
|worf.loganius.retro
|172.23.0.55
|ILS Server (for MS NetMeeting)
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>740bafdb0b18316195d4fa5ede72dafe9e3e9e1c</sha1>
  </revision>
  <revision>
    <id>263</id>
    <parentid>262</parentid>
    <timestamp>2025-08-30T15:05:21Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Add the new members to the list of IP allocations</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4900" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|Servers at /dev/hack
| -
|172.23.3/22
|172.23.0.1
|May add more servers/services physically located at /dev/hack so might as well give them an IP range
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|-
|pmc
|Unknown
|100.89.128.33
|100.96.33.0/24
| -
|-
|kirb
|Unknown
|100.89.128.34
|100.96.34.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|kirk.loganius.retro
|100.96.9.3
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|kirk.loganius.retro
|100.96.9.3
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|Cursed
|107
|cghmn-mail.retro
|172.23.0.69
|Mail Server
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|-
|Loganius
|109
|worf.loganius.retro
|172.23.0.55
|ILS Server (for MS NetMeeting)
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>923736b51e5aeeaf8f5d0b0112e1983170301b7f</sha1>
  </revision>
  <revision>
    <id>264</id>
    <parentid>263</parentid>
    <timestamp>2025-08-30T15:46:15Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>/dev/hack is dead to us</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4839" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|VMs on the OVH Box
| -
|172.23.3/22
|172.23.0.1
|Servers running on KS-1 box at OVH Canada
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the  network. Members receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|-
|pmc
|Unknown
|100.89.128.33
|100.96.33.0/24
| -
|-
|kirb
|Unknown
|100.89.128.34
|100.96.34.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|kirk.loganius.retro
|100.96.9.3
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|kirk.loganius.retro
|100.96.9.3
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|Cursed
|107
|cghmn-mail.retro
|172.23.0.69
|Mail Server
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|-
|Loganius
|109
|worf.loganius.retro
|172.23.0.55
|ILS Server (for MS NetMeeting)
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>2ce361fcca9b04eb0e57d04505143cf8524ef1f7</sha1>
  </revision>
  <revision>
    <id>265</id>
    <parentid>264</parentid>
    <timestamp>2025-09-01T05:24:04Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>I got approval to use 100.96.0.0/24 for single IP allocations. Writing this down so we don't forget.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5010" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|VMs on the OVH Box
| -
|172.23.3/22
|172.23.0.1
|Servers running on KS-1 box at OVH Canada
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the network. Members which need routed subnets receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default. Members who only need single IPs receive an IP from the &lt;code&gt;100.96.0.0/24&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|-
|pmc
|Unknown
|100.89.128.33
|100.96.33.0/24
| -
|-
|kirb
|Unknown
|100.89.128.34
|100.96.34.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|kirk.loganius.retro
|100.96.9.3
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|kirk.loganius.retro
|100.96.9.3
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|Cursed
|107
|cghmn-mail.retro
|172.23.0.69
|Mail Server
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|-
|Loganius
|109
|worf.loganius.retro
|172.23.0.55
|ILS Server (for MS NetMeeting)
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>d7aaf7040617cf23fa3c3e06d37da91379286d39</sha1>
  </revision>
  <revision>
    <id>266</id>
    <parentid>265</parentid>
    <timestamp>2025-09-01T05:52:21Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <minor/>
    <comment>Phrasing</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5006" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|VMs on the OVH Box
| -
|172.23.3/22
|172.23.0.1
|Servers running on KS-1 box at OVH Canada
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the network. Members which need routed subnets receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default. Members who only a single IP receive an IP from the &lt;code&gt;100.96.0.0/24&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|-
|pmc
|Unknown
|100.89.128.33
|100.96.33.0/24
| -
|-
|kirb
|Unknown
|100.89.128.34
|100.96.34.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|kirk.loganius.retro
|100.96.9.3
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|kirk.loganius.retro
|100.96.9.3
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|Cursed
|107
|cghmn-mail.retro
|172.23.0.69
|Mail Server
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|-
|Loganius
|109
|worf.loganius.retro
|172.23.0.55
|ILS Server (for MS NetMeeting)
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>46f6ef532446e5f5f1016e2238499751d1c97918</sha1>
  </revision>
  <revision>
    <id>267</id>
    <parentid>266</parentid>
    <timestamp>2025-09-01T17:43:31Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Add GothPanda's new single IP allocation</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5053" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|VMs on the OVH Box
| -
|172.23.3/22
|172.23.0.1
|Servers running on KS-1 box at OVH Canada
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the network. Members which need routed subnets receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default. Members who only a single IP receive an IP from the &lt;code&gt;100.96.0.0/24&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|-
|pmc
|Unknown
|100.89.128.33
|100.96.33.0/24
| -
|-
|kirb
|Unknown
|100.89.128.34
|100.96.34.0/24
| -
|-
|GothPanda
|Unknwon
|100.96.0.1
|N/A
|Proxy
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|kirk.loganius.retro
|100.96.9.3
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|kirk.loganius.retro
|100.96.9.3
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|Cursed
|107
|cghmn-mail.retro
|172.23.0.69
|Mail Server
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|-
|Loganius
|109
|worf.loganius.retro
|172.23.0.55
|ILS Server (for MS NetMeeting)
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>128c9f26ededad9bca5afc7620a9852ad5d663a5</sha1>
  </revision>
  <revision>
    <id>270</id>
    <parentid>267</parentid>
    <timestamp>2025-09-04T00:21:16Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Add my new IP allocation</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5128" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|VMs on the OVH Box
| -
|172.23.3/22
|172.23.0.1
|Servers running on KS-1 box at OVH Canada
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the network. Members which need routed subnets receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default. Members who only a single IP receive an IP from the &lt;code&gt;100.96.0.0/24&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|-
|pmc
|Unknown
|100.89.128.33
|100.96.33.0/24
| -
|-
|kirb
|Unknown
|100.89.128.34
|100.96.34.0/24
| -
|-
|GothPanda
|Unknwon
|100.96.0.1
|N/A
|Proxy
|-
|loganius
|Lenovo Yoga 6 that's falling apart.
|100.96.0.2
|N/A
|Travel
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|kirk.loganius.retro
|100.96.9.3
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|kirk.loganius.retro
|100.96.9.3
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|Cursed
|107
|cghmn-mail.retro
|172.23.0.69
|Mail Server
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|-
|Loganius
|109
|worf.loganius.retro
|172.23.0.55
|ILS Server (for MS NetMeeting)
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>661149fb772b8052b8cf82b57be3cf661fd5da09</sha1>
  </revision>
  <revision>
    <id>271</id>
    <parentid>270</parentid>
    <timestamp>2025-09-04T00:21:39Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Consistent capitalization</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5128" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|VMs on the OVH Box
| -
|172.23.3/22
|172.23.0.1
|Servers running on KS-1 box at OVH Canada
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the network. Members which need routed subnets receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default. Members who only a single IP receive an IP from the &lt;code&gt;100.96.0.0/24&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|-
|pmc
|Unknown
|100.89.128.33
|100.96.33.0/24
| -
|-
|kirb
|Unknown
|100.89.128.34
|100.96.34.0/24
| -
|-
|GothPanda
|Unknwon
|100.96.0.1
|N/A
|Proxy
|-
|Loganius
|Lenovo Yoga 6 that's falling apart.
|100.96.0.2
|N/A
|Travel
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|kirk.loganius.retro
|100.96.9.3
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|kirk.loganius.retro
|100.96.9.3
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|Cursed
|107
|cghmn-mail.retro
|172.23.0.69
|Mail Server
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|-
|Loganius
|109
|worf.loganius.retro
|172.23.0.55
|ILS Server (for MS NetMeeting)
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>9a9dfa06dc1ddb1ac45bedbecc497dfc2017a85a</sha1>
  </revision>
  <revision>
    <id>272</id>
    <parentid>271</parentid>
    <timestamp>2025-09-07T19:32:51Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <minor/>
    <comment>Typo</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5128" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|VMs on the OVH Box
| -
|172.23.3/22
|172.23.0.1
|Servers running on KS-1 box at OVH Canada
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the network. Members which need routed subnets receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default. Members who only a single IP receive an IP from the &lt;code&gt;100.96.0.0/24&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|-
|pmc
|Unknown
|100.89.128.33
|100.96.33.0/24
| -
|-
|kirb
|Unknown
|100.89.128.34
|100.96.34.0/24
| -
|-
|GothPanda
|Unknown
|100.96.0.1
|N/A
|Proxy
|-
|Loganius
|Lenovo Yoga 6 that's falling apart.
|100.96.0.2
|N/A
|Travel
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|kirk.loganius.retro
|100.96.9.3
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|kirk.loganius.retro
|100.96.9.3
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|Cursed
|107
|cghmn-mail.retro
|172.23.0.69
|Mail Server
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|-
|Loganius
|109
|worf.loganius.retro
|172.23.0.55
|ILS Server (for MS NetMeeting)
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>d625adf29bfc6452e26d800d5f497cbe8ab31268</sha1>
  </revision>
  <revision>
    <id>273</id>
    <parentid>272</parentid>
    <timestamp>2025-09-14T00:24:35Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Added i430vx and rwf93</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5237" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|VMs on the OVH Box
| -
|172.23.3/22
|172.23.0.1
|Servers running on KS-1 box at OVH Canada
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the network. Members which need routed subnets receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default. Members who only a single IP receive an IP from the &lt;code&gt;100.96.0.0/24&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|-
|pmc
|Unknown
|100.89.128.33
|100.96.33.0/24
| -
|-
|kirb
|Unknown
|100.89.128.34
|100.96.34.0/24
| -
|-
|GothPanda
|Unknown
|100.96.0.1
|N/A
|Proxy
|-
|Loganius
|Lenovo Yoga 6 that's falling apart.
|100.96.0.2
|N/A
|Travel
|-
|i430vx
|Unknown
|100.89.128.35
|100.96.35.0/24
| -
|-
|rwf93
|Unknown
|100.89.128.36
|100.96.36.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|kirk.loganius.retro
|100.96.9.3
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|kirk.loganius.retro
|100.96.9.3
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|Cursed
|107
|cghmn-mail.retro
|172.23.0.69
|Mail Server
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|-
|Loganius
|109
|worf.loganius.retro
|172.23.0.55
|ILS Server (for MS NetMeeting)
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>767a70a62dd76d29dd3c5f5e12c04c70dc0502e2</sha1>
  </revision>
  <revision>
    <id>274</id>
    <parentid>273</parentid>
    <timestamp>2025-09-21T23:58:50Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Added accipitroid's allocation</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5297" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|VMs on the OVH Box
| -
|172.23.3/22
|172.23.0.1
|Servers running on KS-1 box at OVH Canada
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the network. Members which need routed subnets receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default. Members who only a single IP receive an IP from the &lt;code&gt;100.96.0.0/24&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|-
|pmc
|Unknown
|100.89.128.33
|100.96.33.0/24
| -
|-
|kirb
|Unknown
|100.89.128.34
|100.96.34.0/24
| -
|-
|GothPanda
|Unknown
|100.96.0.1
|N/A
|Proxy
|-
|Loganius
|Lenovo Yoga 6 that's falling apart.
|100.96.0.2
|N/A
|Travel
|-
|i430vx
|Unknown
|100.89.128.35
|100.96.35.0/24
| -
|-
|rwf93
|Unknown
|100.89.128.36
|100.96.36.0/24
| -
|-
|accipitroid
|Unknown
|100.89.128.37
|100.96.37.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|kirk.loganius.retro
|100.96.9.3
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|kirk.loganius.retro
|100.96.9.3
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|Cursed
|107
|cghmn-mail.retro
|172.23.0.69
|Mail Server
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|-
|Loganius
|109
|worf.loganius.retro
|172.23.0.55
|ILS Server (for MS NetMeeting)
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>d8be05e7b5ea602b9bbe4a2cd15383e859ce5785</sha1>
  </revision>
  <revision>
    <id>287</id>
    <parentid>274</parentid>
    <timestamp>2025-10-18T16:00:19Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>omitted a word</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5302" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|VMs on the OVH Box
| -
|172.23.3/22
|172.23.0.1
|Servers running on KS-1 box at OVH Canada
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the network. Members which need routed subnets receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default. Members who only need a single IP receive an IP from the &lt;code&gt;100.96.0.0/24&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|-
|pmc
|Unknown
|100.89.128.33
|100.96.33.0/24
| -
|-
|kirb
|Unknown
|100.89.128.34
|100.96.34.0/24
| -
|-
|GothPanda
|Unknown
|100.96.0.1
|N/A
|Proxy
|-
|Loganius
|Lenovo Yoga 6 that's falling apart.
|100.96.0.2
|N/A
|Travel
|-
|i430vx
|Unknown
|100.89.128.35
|100.96.35.0/24
| -
|-
|rwf93
|Unknown
|100.89.128.36
|100.96.36.0/24
| -
|-
|accipitroid
|Unknown
|100.89.128.37
|100.96.37.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|kirk.loganius.retro
|100.96.9.3
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|kirk.loganius.retro
|100.96.9.3
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|Cursed
|107
|cghmn-mail.retro
|172.23.0.69
|Mail Server
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|-
|Loganius
|109
|worf.loganius.retro
|172.23.0.55
|ILS Server (for MS NetMeeting)
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>b38b855692159a5463b4dadd90cf29bbb4c4fc15</sha1>
  </revision>
  <revision>
    <id>288</id>
    <parentid>287</parentid>
    <timestamp>2025-10-18T16:46:04Z</timestamp>
    <contributor>
      <username>Loganius</username>
      <id>6</id>
    </contributor>
    <comment>Added Elim</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5388" xml:space="preserve">=== IP Address Allocations in the CGHMN Network ===
This page documents any IP addresses that are allocated statically to routers, subnets and members.

=== Networks on the CGHMN side ===
This is a list of all networks active on the CGHMN server side.
{| class="wikitable"
|+
!Network Name
!VLAN
!Subnet
!Router IP
!Notes
|-
|Core Services
|4
|172.23.4.0/22
|172.23.4.1
| -
|-
|Servers
|8
|172.23.8.0/22
|172.23.8.1
| -
|-
|Global LAN
|256
| -
| -
|No IP traffic, no assigned IP addresses
|-
|Wireguard Members Tunnel
| -
|100.89.128.0/22
|100.89.128.0
|The .0 for the router is not a typo, on P2P links the network address can also be used for a host
|-
|VMs on the OVH Box
| -
|172.23.3/22
|172.23.0.1
|Servers running on KS-1 box at OVH Canada
|}

=== Members' Networks ===
This list contains the subnets that are assigned to member routers on the network. Members which need routed subnets receive one &lt;code&gt;/24&lt;/code&gt; network from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; block, in first-come-first-serve sequential order per default. Members who only need a single IP receive an IP from the &lt;code&gt;100.96.0.0/24&lt;/code&gt; block, in first-come-first-serve sequential order per default.
{| class="wikitable"
|+
!Member Name
!Peer Endpoint/Via
!Tunnel IP
!Routed Subnet(s)
!Notes
|-
|CursedSilicon
|/dev/hack (usually)
|100.89.128.1
|100.96.1.0/24
| -
|-
|Talija
| DIY
|100.89.128.2
|100.96.2.0/24
| -
|-
|Snep
|OPNsense box and PPPoE server
|100.89.128.3
|100.96.3.0/24
| -
|-
|Snep
|PC VPN tunnel
|100.89.128.4
| -
| -
|-
|Hadn69
| DIY
|100.89.128.5
|100.96.5.0/24
| -
|-
|Lily
| Dell PowerEdge R620
|100.89.128.6
|100.96.6.0/24
| -
|-
|Theothertom
| Unknown
|100.89.128.7
|100.96.7.0/24
| -
|-
|Lily
| Raspberry Pi
|100.89.128.8
|100.96.8.0/24
| -
|-
|Loganius
| PPTP Bridge on Debian VM
|100.89.128.9
|100.96.9.0/24
| Using Microsoft Virtual Server 2005 under Windows Server 2003.
|-
|GothPanda
| OpenWRT
|100.89.128.10
|100.96.10.0/24
| TP-Link Archer C59 v2
|-
|ch0ccyra1n
| Unknown
|100.89.128.11
|100.96.11.0/24
| -
|-
|Chromaryu
|Unknown
|100.89.128.12
|100.96.12.0/24
| -
|-
|Serena
|Unknown
|100.89.128.13
|100.96.13.0/24
|Chivanet
|-
|CursedSilicon
|OpenWRT VM
|100.89.128.14
|100.96.14.0/24
|At home
|-
|Mel
|OpenWRT VM
|100.89.128.15
|100.96.15.0/24
|"Glinet Nugget"
|-
|Spz2024
|OpenWRT VM
|100.89.128.16
|100.96.16.0/24
| OpenWRT in QEMU on Windows host
|-
|Spaztron64
|Unknown
|100.89.128.17
|100.96.17.0/24
| -
|-
|Harry
|Unknown
|100.89.128.18
|100.96.18.0/24
| -
|-
|Mel
|OpenWRT VM
|100.89.128.19
|100.96.19.0/24
|OpenWRT VM 
|-
|Spaztron64
|Unknown
|100.89.128.20
|100.96.20.0/24
| -
|-
|TsuboDii
|Unknown
|100.89.128.21
|100.96.21.0/24
| -
|-
|j4yc33
|Unknown
|100.89.128.22
|100.96.22.0/24
| -
|-
|CursedSilicon
|Unknown
|100.89.128.23
|100.96.23.0/24
|"Travel Router"
|-
|Dusty
|Unknown
|100.89.128.24
|100.96.24.0/24
| -
|-
|Nicuuut
|Unknown
|100.89.128.25
|100.96.25.0/24
| -
|-
|Tyler McVicker
|Unknown
|100.89.128.26
|100.96.26.0/24
|"Game Servers"
|-
|YoungChief
|Unknown
|100.89.128.27
|100.96.27.0/24
| -
|-
|Zefie
|Unknown
|100.89.128.28
|100.96.28.0/24
| -
|-
|CH
|Unknown
|100.89.128.29
|100.96.29.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.30
|100.96.30.0/24
| -
|-
|Alyx
|Unknown
|100.89.128.31
|100.96.31.0/24
|"Datacenter"
|-
|Grawity
|Unknown
|100.89.128.32
|100.96.32.0/24
| -
|-
|pmc
|Unknown
|100.89.128.33
|100.96.33.0/24
| -
|-
|kirb
|Unknown
|100.89.128.34
|100.96.34.0/24
| -
|-
|GothPanda
|Unknown
|100.96.0.1
|N/A
|Proxy
|-
|Loganius
|Lenovo Yoga 6 that's falling apart.
|100.96.0.2
|N/A
|Travel
|-
|i430vx
|Unknown
|100.89.128.35
|100.96.35.0/24
| -
|-
|rwf93
|Unknown
|100.89.128.36
|100.96.36.0/24
| -
|-
|accipitroid
|Unknown
|100.89.128.37
|100.96.37.0/24
| -
|}

=== Member-Delegated (Sub-) Domains ===
{| class="wikitable"
|+
!Member Name
!Domain
!Nameserver
!Nameserver IP
!Notes
|-
|Serena
|chivanet
|pandora.chivanet
|100.96.13.7
| -
|-
|Nicuuut
|goat
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Talija
|coyote.retro
|a.ns.coyote.retro
|100.96.2.53
| -
|-
|''Snep''
|''snep.retro''
|''ns1.snep.retro''
|''172.23.8.11''
| Currently offline
|-
|Lily
|lily.retro
|ns1.lily.retro
|100.96.6.250
| -
|-
|Loganius
|loganius.retro
|kirk.loganius.retro
|100.96.9.3
| -
|-
|theothertom
|theothertom.retro
|north-foreland.theothertom.retro
|100.96.7.12
| -
|-
|Spaztron64
|arcesia.retro
|ns.arcesia.retro
|100.96.17.105
| -
|-
|ch0ccyra1n
|oohay.retro
|ns1.oohay.retro
|100.96.11.197
| -
|-
|Harry
|404.retro
|ns.404.retro
|100.96.18.254
| -
|-
|GothPanda
|northstar.retro
|ns1.northstar.retro
|172.23.3.201
| -
|-
|Loganius
|askme.retro
|kirk.loganius.retro
|100.96.9.3
| -
|}

=== Member Servers hosted on the CGHMN side ===
{| class="wikitable"
|+
!Member Name
!VM/CT ID
!Server Name
!Server IP
!Notes
|-
|Snep
|10811
|srv01.snep.retro
|172.23.8.11
| -
|-
|Talija
|118
|junko.coyote.retro
|172.23.3.173
|Network diagnostics
|-
|Loganius
|123
|kira.loganius.retro
|172.23.0.52
|WMS Server
|-
|Cursed
|107
|cghmn-mail.retro
|172.23.0.69
|Mail Server
|-
|Nicuuut
|124
|sanemi.nicuuut.goat
|172.23.0.53
| -
|-
|Nicuuut
|103
|mitsuri.nicuuut.goat
|172.23.0.54
| -
|-
|GothPanda
|104
|litwick.northstar.retro
|172.23.3.201
|also hosts tests.cghmn
|-
|Loganius
|109
|worf.loganius.retro
|172.23.0.55
|ILS Server (for MS NetMeeting)
|-
|Loganius
|10056
|elim.loganius.retro
|172.23.0.56
|Minecraft Reverse Proxy Server
|}
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>f2ad4049bb0b6e0c9920cba1862e5c6f28af279b</sha1>
  </revision>
</page>
<page arvcontinue="20250816031124|259">
  <title>Services people are running</title>
  <ns>0</ns>
  <id>91</id>
  <revision>
    <id>268</id>
    <parentid>256</parentid>
    <timestamp>2025-09-03T15:35:04Z</timestamp>
    <contributor>
      <username>Ch0ccyra1n</username>
      <id>14</id>
    </contributor>
    <minor/>
    <comment>Update status of oohay.retro to be accurate</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4491" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
{| class="wikitable"
|+
!Hostname
!Port (non-TLS)
!TLS?
!Notes
|-
|irc.cghmn.retro
|6667
|no
|Bridged onto the regular internet and Discord
|-
|irc.loganius.retro
|6667
|yes, at 6697
|Must register your nick with NickServ before you can start talking. You'll need working email for this.
|}

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: SSL is ''enabled'' but is not widely tested. Your mileage may vary. If you experience issues, just use insecure/plaintext modes for simplicity'''

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.6
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|-
|Serena
|wow.chivanet
|100.96.13.13
|World of Warcraft 3.3.5a (Wrath of the Lich King)
|Linux
|Message Serena for an account
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or http://live.loganius.retro:81/&lt;/nowiki&gt;
|-
|Loganius
|askme.retro
|Windows Server 2003 R2
|IIS 6.0
|The AskMe Search Engine
|
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|-
|ch0ccyra1n
|oohay.retro
|Ubuntu Server
|Nginx
|A CGHMN Service Provider
|Currently down, will be up eventually.
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at forum.theothertom.retro. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Google Search Appliance ===
Available on '''google.retro'''

'''Submit domains for indexing to CursedSilicon. Crawling takes about 15 minutes'''

=== Pandia Search ===
Available on '''''www.chivanet''''' (no TLD but WWW is required!)

Has both a web and CGHMN version (automatically selected by detecting the domain from which the user visits)

'''Sites can be added via the Pandia UI'''

=== AskMe ===
Available on '''askme.retro'''

'''Must submit pages for indexing'''
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>db578859e05772e9c304a7f6cac1662e8199d0b4</sha1>
  </revision>
  <revision>
    <id>269</id>
    <parentid>268</parentid>
    <timestamp>2025-09-03T15:37:42Z</timestamp>
    <contributor>
      <username>Ch0ccyra1n</username>
      <id>14</id>
    </contributor>
    <minor/>
    <comment>Add links for different services</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4605" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network.

=== IRC ===
{| class="wikitable"
|+
!Hostname
!Port (non-TLS)
!TLS?
!Notes
|-
|irc.cghmn.retro
|6667
|no
|Bridged onto the regular internet and Discord
|-
|irc.loganius.retro
|6667
|yes, at 6697
|Must register your nick with NickServ before you can start talking. You'll need working email for this.
|}

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: SSL is ''enabled'' but is not widely tested. Your mileage may vary. If you experience issues, just use insecure/plaintext modes for simplicity'''

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.6
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|-
|Serena
|wow.chivanet
|100.96.13.13
|World of Warcraft 3.3.5a (Wrath of the Lich King)
|Linux
|Message Serena for an account
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or &lt;/nowiki&gt;http://live.loganius.retro:81/
|-
|Loganius
|askme.retro
|Windows Server 2003 R2
|IIS 6.0
|The AskMe Search Engine
|
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|-
|ch0ccyra1n
|oohay.retro
|Ubuntu Server
|Nginx
|A CGHMN Service Provider
|Currently down, will be up eventually.
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN Proxmox Hosting ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at [http://forum.theothertom.retro forum.theothertom.retro]. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Google Search Appliance ===
Available on '''[http://google.retro google.retro]'''

'''Submit domains for indexing to CursedSilicon. Crawling takes about 15 minutes'''

=== Pandia Search ===
Available on '''''[http://www.chivanet www.chivanet]''''' (no TLD but WWW is required!)

Has both a web and CGHMN version (automatically selected by detecting the domain from which the user visits)

'''Sites can be added via the Pandia UI'''

=== AskMe ===
Available on '''[http://askme.retro askme.retro]'''

'''Must submit pages for indexing'''
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>6f0559d61af0153474faf1eba9fc2cdc2fc2d77f</sha1>
  </revision>
  <revision>
    <id>277</id>
    <parentid>269</parentid>
    <timestamp>2025-10-01T18:21:17Z</timestamp>
    <contributor>
      <username>Ch0ccyra1n</username>
      <id>14</id>
    </contributor>
    <minor/>
    <comment>/* AIM */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4641" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network with a [[AIM Clients|client]].

=== IRC ===
{| class="wikitable"
|+
!Hostname
!Port (non-TLS)
!TLS?
!Notes
|-
|irc.cghmn.retro
|6667
|no
|Bridged onto the regular internet and Discord
|-
|irc.loganius.retro
|6667
|yes, at 6697
|Must register your nick with NickServ before you can start talking. You'll need working email for this.
|}

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: SSL is ''enabled'' but is not widely tested. Your mileage may vary. If you experience issues, just use insecure/plaintext modes for simplicity'''

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.6
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|-
|Serena
|wow.chivanet
|100.96.13.13
|World of Warcraft 3.3.5a (Wrath of the Lich King)
|Linux
|Message Serena for an account
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or &lt;/nowiki&gt;http://live.loganius.retro:81/
|-
|Loganius
|askme.retro
|Windows Server 2003 R2
|IIS 6.0
|The AskMe Search Engine
|
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|-
|ch0ccyra1n
|oohay.retro
|Ubuntu Server
|Nginx
|A CGHMN Service Provider
|Currently down, will be up eventually.
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN Proxmox Hosting ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at [http://forum.theothertom.retro '''forum.theothertom.retro''']. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== TODO: A pastebin ===
Would be good for sharing logs etc.

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Google Search Appliance ===
Available on '''[http://google.retro google.retro]'''

'''Submit domains for indexing to CursedSilicon. Crawling takes about 15 minutes'''

=== Pandia Search ===
Available on '''''[http://www.chivanet www.chivanet]''''' (no TLD but WWW is required!)

Has both a web and CGHMN version (automatically selected by detecting the domain from which the user visits)

'''Sites can be added via the Pandia UI'''

=== AskMe ===
Available on '''[http://askme.retro askme.retro]'''

'''Must submit pages for indexing'''
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>c8bf30712846fc2eb5149f4434b7646947a0315d</sha1>
  </revision>
  <revision>
    <id>279</id>
    <parentid>277</parentid>
    <timestamp>2025-10-05T19:43:38Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>We have a Pastebin!</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4632" xml:space="preserve">This is a collection of "services" available on CGHMN. It's intended as a bootstrapping point until we get something to help with discovery. Feel free to add your own services!

== Chat ==

=== AIM ===
CGHMN connects to Chivanet's AIM service (running RetroAimServer). To use it, you need to sign up via http://chivanet.org/aim/. Once you have a screenname, you can connect from within the network with a [[AIM Clients|client]].

=== IRC ===
{| class="wikitable"
|+
!Hostname
!Port (non-TLS)
!TLS?
!Notes
|-
|irc.cghmn.retro
|6667
|no
|Bridged onto the regular internet and Discord
|-
|irc.loganius.retro
|6667
|yes, at 6697
|Must register your nick with NickServ before you can start talking. You'll need working email for this.
|}

=== MSN Messenger ===
'''TODO (maybe ask to federate with NINA ala ChivaNet?) - CursedSilicon'''

== Email ==
You can run your own mail server on a .retro domain. If you would prefer not to (or want a backup), there are some open mail services (separate from general "hosting").

=== CGHMN Public Email Service (ala Hotmail/Yahoo/Gmail) ===
Webmail: available - Supports Internet Explorer 3 (in theory) as a minimum. IE5 on Win3.11 tested and verified working.

HTTP: http://cghmn-mail.retro

IMAP:: cghmn-mail.retro

POP3: cghmn-mail.retro

(both incoming and outgoing servers use the same address for POP/IMAP/SMTP)

'''NOTE: SSL is ''enabled'' but is not widely tested. Your mileage may vary. If you experience issues, just use insecure/plaintext modes for simplicity'''

How to sign up: message cursedsilicon on IRC/Discord.

== Game servers ==
{| class="wikitable"
|+
!User
!Hostname
!IP
!Game(s)
!OS
!Notes
|-
|Loganius
|loganius.retro
|100.96.9.6
|ClassiCube &amp; Halo PC
|Windows Server 2003 R2
|Must connect by IP for Halo.
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Battle.Net
|Linux
|Just works! Plays Blizzard games up to Warcraft 3: Frozen Throne
|-
|CursedSilicon
|cursedsilicon.retro
|172.23.0.20
|Westwood Online
|Linux
|Just works! Plays Westwood games up to Red Alert 2: Yuri's Revenge
|-
|Serena
|wow.chivanet
|100.96.13.13
|World of Warcraft 3.3.5a (Wrath of the Lich King)
|Linux
|Message Serena for an account
|}
'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''

== Websites ==
{| class="wikitable"
|+
!User
!IP/Hostname
!OS
!Server
!Brief Description
!Notes
|-
|Loganius
|loganius.retro
|Windows Server 2003 R2
|IIS 6.0
|Whatever I feel like putting there.
|Supports HTTPS.
|-
|Loganius
|live.loganius.retro
|Windows Server 2003 R2 x64
|IIS 6.0
|My livestream VODs.
|&lt;nowiki&gt;Livestreams at [rtsp | mms]://live.loganius.retro/, or &lt;/nowiki&gt;http://live.loganius.retro:81/
|-
|Loganius
|askme.retro
|Windows Server 2003 R2
|IIS 6.0
|The AskMe Search Engine
|
|-
|CursedSilicon
|cursedsilicon.retro
|Linux
|Nginx
|Basically a landing page for new users. 
Also has an FTP with lots of useful files
|Also available at http://cghmn.cursedsilicon.net
|-
|ch0ccyra1n
|oohay.retro
|Ubuntu Server
|Nginx
|A CGHMN Service Provider
|Currently down, will be up eventually.
|}
== Hosting ==

=== Theotherhost ===
{| class="wikitable"
|+
!OS
!Platform
!Admin UI requirements
!Languages
!Databases
!Services
|-
|Linux
|BlueOnyx
|IE 5 (tested on Win 2k)
|Perl 5.8.8, PHP 5.1.5
|MySQL 5.0.95
|FTP/Web/SMTP/IMAP/POP/DNS/Mailing lists
|}
'''How to sign up: message theothertom on IRC.'''

=== CGHMN Proxmox Hosting ===
CGHMN will offer Proxmox based hosting in future. Currently we are limited by hard disk capacity, but small servers can be uploaded and run. Ask CursedSilicon for details. 

== Other communications ==

=== theotherforum ===
There is a forum at [http://forum.theothertom.retro '''forum.theothertom.retro''']. This can be used to share projects/sites, as well as for general discussion. Currently, you need an email address to sign up.

=== Pastebin ===
http://wastebin.retro thanks Alyx!

=== TODO: Image host ===
Somewhere for screenshots etc.

=== TODO: webring ===
To help find sites

== Search ==

=== Google Search Appliance ===
Available on '''[http://google.retro google.retro]'''

'''Submit domains for indexing to CursedSilicon. Crawling takes about 15 minutes'''

=== Pandia Search ===
Available on '''''[http://www.chivanet www.chivanet]''''' (no TLD but WWW is required!)

Has both a web and CGHMN version (automatically selected by detecting the domain from which the user visits)

'''Sites can be added via the Pandia UI'''

=== AskMe ===
Available on '''[http://askme.retro askme.retro]'''

'''Must submit pages for indexing'''
[[Category:Compu-Global-Hyper-Mega-Net]]</text>
    <sha1>a124b45ea742df86e5d57f7d38f4c0b2c134dad0</sha1>
  </revision>
</page>
<page arvcontinue="20250816031124|259">
  <title>.retro</title>
  <ns>0</ns>
  <id>93</id>
  <revision>
    <id>275</id>
    <timestamp>2025-10-01T18:15:50Z</timestamp>
    <contributor>
      <username>Ch0ccyra1n</username>
      <id>14</id>
    </contributor>
    <comment>Create page for .retro TLD</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="375" xml:space="preserve">'''.retro''' is a [[Compu-Global-Hyper-Mega-Net]] ([[Compu-Global-Hyper-Mega-Net|CGHMN]]) [[top-level domain]] ([[Top-level domain|TLD]]). Created in the first group of TLDs alongside [[.cghmn]], it serves as a generic TLD for sites on CGHMN and is administered by [[User:CursedSilicon|CursedSilicon]]. 
[[Category:Compu-Global-Hyper-Mega-Net]]
[[Category:Top-level domains]]</text>
    <sha1>5da8b1bb173daa0d83d66de28c3bc1e8b75fea80</sha1>
  </revision>
</page>
<page arvcontinue="20250816031124|259">
  <title>.cghmn</title>
  <ns>0</ns>
  <id>94</id>
  <revision>
    <id>276</id>
    <timestamp>2025-10-01T18:17:46Z</timestamp>
    <contributor>
      <username>Ch0ccyra1n</username>
      <id>14</id>
    </contributor>
    <comment>Create page for .cghmn TLD</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="362" xml:space="preserve">'''.cghmn''' is a [[Compu-Global-Hyper-Mega-Net]] ([[Compu-Global-Hyper-Mega-Net|CGHMN]]) [[top-level domain]] ([[Top-level domain|TLD]]). Created in the first group of TLDs alongside .retro, it serves as a TLD for sites on CGHMN and is administered by [[User:CursedSilicon|CursedSilicon]].
[[Category:Compu-Global-Hyper-Mega-Net]]
[[Category:Top-level domains]]</text>
    <sha1>6be469f2769ea9d860fc6df827c1658282fc12ab</sha1>
  </revision>
</page>
<page arvcontinue="20250816031124|259">
  <title>CGHMN 1.0</title>
  <ns>0</ns>
  <id>79</id>
  <revision>
    <id>278</id>
    <parentid>169</parentid>
    <timestamp>2025-10-01T18:29:58Z</timestamp>
    <contributor>
      <username>Ch0ccyra1n</username>
      <id>14</id>
    </contributor>
    <comment>Add my own suggestion for onboarding improvements</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="801" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
== Tracking sheet for "what would we want in a general 1.0 release" ==

Let's break these down by user just to keep division of labor easy

=== CursedSilicon suggestions ===


The main blocker currently is access to reliable fiber at /dev/hack. Gaining that should give us ample bandwidth to start allowing broader user access to the network generally

Maybe invite a selection of "retro networking" youtube folks (TheSerialPort, ClabRetro, etc) to help tire kick things? Serena also suggested federation of retro network service providers, so this could be a useful step.

=== ch0ccyra1n suggestions ===
We should ensure that there is a better way to do onboarding. Some sort of web form on the clearnet for signups (or signup requests) would be good to have.</text>
    <sha1>5cdd11c970bdc3a87a7fd5fb77bb4ebc5e08f95a</sha1>
  </revision>
  <revision>
    <id>280</id>
    <parentid>278</parentid>
    <timestamp>2025-10-06T19:31:47Z</timestamp>
    <contributor>
      <username>Ch0ccyra1n</username>
      <id>14</id>
    </contributor>
    <minor/>
    <comment>/* ch0ccyra1n suggestions */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="845" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
== Tracking sheet for "what would we want in a general 1.0 release" ==

Let's break these down by user just to keep division of labor easy

=== CursedSilicon suggestions ===


The main blocker currently is access to reliable fiber at /dev/hack. Gaining that should give us ample bandwidth to start allowing broader user access to the network generally

Maybe invite a selection of "retro networking" youtube folks (TheSerialPort, ClabRetro, etc) to help tire kick things? Serena also suggested federation of retro network service providers, so this could be a useful step.

=== ch0ccyra1n suggestions ===
We should ensure that there is a better way to do onboarding. Some sort of web form on the clearnet for signups (or signup requests) would be good to have.&lt;sup&gt;[[https://signup.cghmn.org done]]&lt;/sup&gt;</text>
    <sha1>f264cc41ef9932bb4d7933db6073abe90ac98916</sha1>
  </revision>
  <revision>
    <id>300</id>
    <parentid>280</parentid>
    <timestamp>2025-10-28T23:53:24Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="777" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
== Tracking sheet for "what would we want in a general 1.0 release" ==

Let's break these down by user just to keep division of labor easy. This isn't a "we will do this" so much as a "request for comments"

=== CursedSilicon suggestions ===

We can trivially set up an OpenWRT build bot. But a custom splash screen that just asks for a users Wireguard+IP details would be fantastic for user onboarding. Need someone who can write Lua to do this though

=== ch0ccyra1n suggestions ===
&lt;s&gt;We should ensure that there is a better way to do onboarding. Some sort of web form on the clearnet for signups (or signup requests) would be good to have.&lt;big&gt;'''&lt;sup&gt;[&lt;/sup&gt;'''&lt;/big&gt;&lt;/s&gt;&lt;big&gt;'''&lt;sup&gt;[https://signup.cghmn.org done]]&lt;/sup&gt;'''&lt;/big&gt;</text>
    <sha1>7c36bd80850b95d25c8337b079e9a06ba4a61184</sha1>
  </revision>
</page>
<page arvcontinue="20250816031124|259">
  <title>Signup</title>
  <ns>0</ns>
  <id>75</id>
  <revision>
    <id>281</id>
    <parentid>172</parentid>
    <timestamp>2025-10-06T21:44:01Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Re-written for Open Beta</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3454" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
Compu-Global-Hyper-Mega-Net is now in '''''OPEN BETA!''''' That means if you're reading this, you've either filled out our signup page and gotten sent an email, or stumbled across this page on the Wiki. 


Either way, welcome!


So. To get ON Compu-Global-Hyper-Mega-Net (hereby referred to as CGHMN for easier reference) you'll need a few things.

# A retro computer or device that can be terminated via ethernet. Using other networking standards like 802.11, Token Ring, AUI and others is totally fine, but you'll need to bridge them to ethernet!
# A device that can run the Wireguard and (optionally) Gretap protocols. Wireguard is a VPN stack that is used to encrypt traffic and connect your retro devices securely to the network over the internet. Gretap is used for tunneling "non TCP/IP" protocols, like IPX. Useful if you want to play DOOM or run other esoteric software, '''''but not required!'''''
# To have fun! Seriously. This project is meant to bring back the joy of the web as it existed in the 90's and 2000's. If you aren't having fun, we need to fix that

For Part 2 you can use any kind of device that runs '''''Linux/BSD''''' such as a Raspberry Pi or others. Virtual Machines are also absolutely supported! 


For hardware, we recommend something like the [https://www.gl-inet.com/products/gl-ar300m/ GL.iNet Shadow]. This device retails for around $30~ US dollars on retailers such as Amazon and can push 40 megabits of bandwidth to CGHMN over Wireguard. This is more than sufficient for a significant number of retro machines. This device has been deployed by Cursed Silicon and other users and has been successfully tested at-scale hosting 15 simultaneous users at the Seattle Interim Computer Festival event. 


Another option (if you have one) is the Raspberry Pi. Every Pi version through the original Pi 1 to the current Pi 5 [https://openwrt.org/toh/raspberry_pi_foundation/raspberry_pi are supported]. Adding a cheap USB LAN adapter makes this an attractive option if you have a spare Pi laying around. 


The third option is to run a virtual machine as your CGHMN gateway. We support Proxmox, VMware, Virtualbox, Hyper-V and others. Using CGHMN does not necessarily require using vintage ''hardware'' and doing so can be impractical for a number of reasons. A lot of users (including Cursed Silicon and others) use virtualization to run [[Services people are running|services on the network]] efficiently


Finally if you're particularly proficient with Linux or Networking (or both) you can opt to run your own hardware configured to your specifications. We don't directly provide support for vendors like Microtik, Unifi or others, but during the closed testing we've done in past, users have been able to set these vendor devices up and successfully connect.


We recommend running the [https://openwrt.org/ OpenWRT] router distribution regardless of which option you choose. This supports an enormous array of hardware (including running as a VM) and even comes with a [https://cghmn.snep.zip/connect.sh ready-made script] written by our network architect, Snep. This script can be run on a device running OpenWRT to configure it directly for access to CGHMN.


The commands to run the script are as follows.

# Install OpenWRT and SSH into the device
# &lt;code&gt;wget &lt;nowiki&gt;https://cghmn.snep.zip/connect.sh&lt;/nowiki&gt;&lt;/code&gt;
# &lt;code&gt;ash setup-cghmn.sh&lt;/code&gt;
# Follow the prompts!</text>
    <sha1>a8f6529474d750e04f7bc7751da19e898137b273</sha1>
  </revision>
  <revision>
    <id>282</id>
    <parentid>281</parentid>
    <timestamp>2025-10-07T20:21:53Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Tweaked wordings, updated things to be more clear (hopefully)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4649" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
Compu-Global-Hyper-Mega-Net is now in '''''OPEN BETA!''''' That means if you're reading this, you've either filled out our signup page and gotten sent an email, or stumbled across this page on the Wiki. 


Either way, welcome!


So. To get ON Compu-Global-Hyper-Mega-Net (hereby referred to as CGHMN for easier reference) you'll need a few things.

# A retro computer/virtual machine or a device that can be ultimately terminated via ethernet. Using other networking standards like 802.11, Token Ring, AUI, BNC or others is totally fine, but you'll need to ultimately bridge them to Ethernet to talk to the device running Wireguard 
# A device that can run the Wireguard and (optionally) Gretap protocols. Wireguard is a VPN stack that is used to encrypt traffic and connect your retro devices securely to the network over the internet. Gretap is used for tunneling "non TCP/IP" protocols, like IPX. Useful if you want to play DOOM or run other non-TCP/IP software, '''''but not required!'''''
# To '''have fun!''' Seriously. This project is meant to bring back the joy of the web as it existed in the 90's and 2000's. If you aren't having fun, we need to fix that.

For Step 2 you can use any kind of device that runs '''''Linux/BSD''''' such as a Raspberry Pi or others. Virtual Machines (such as Proxmox) are absolutely supported and encouraged! 


For users looking to connect physical machines, you will need a hardware device. We recommend something like the [https://www.gl-inet.com/products/gl-ar300m/ GL.iNet Shadow]. This device retails for around $30~ US dollars on retailers such as Amazon and can push 40 megabits of bandwidth to CGHMN over Wireguard. This is more than sufficient for a significant number of retro machines. This device has been deployed by Cursed Silicon and other users and has been successfully tested at-scale hosting 15 simultaneous users at the Seattle Interim Computer Festival retro computing event. 


Another option (if you have one) is the Raspberry Pi. Every Pi version through the original Pi 1 to the current Pi 5 [https://openwrt.org/toh/raspberry_pi_foundation/raspberry_pi is supported by OpenWRT]. Adding a cheap USB LAN adapter makes this an attractive option if you have a spare "old Ras Pi laying around" 


The third option is to run a virtual machine as your CGHMN gateway. We provide support primarily for '''''Proxmox''''' but other virtualization stacks such as VMware, Virtualbox and Hyper-V will work, but may require manual configuration by the user. '''This option is best suited for users wanting to run servers (websites, old game servers etc) as running old OSes in Proxmox comes with a significant graphics performance penalty'''  

We recommend running the [https://openwrt.org/ OpenWRT] router distribution regardless of which above option you choose. This supports an enormous array of hardware (including running as a VM) and even comes with a [https://cghmn.snep.zip/connect.sh ready-made script] written by our network architect, Snep. This script can be run on a device running OpenWRT to configure it directly for access to CGHMN.

Once installed in either a VM or on a physical device such as the GL.iNet Shadow, the device can be SSH'd into and the following commands can be run to begin configuration for CGHMN access.

# &lt;code&gt;wget &lt;nowiki&gt;https://cghmn.snep.zip/connect.sh&lt;/nowiki&gt;&lt;/code&gt;
# &lt;code&gt;ash setup-cghmn.sh&lt;/code&gt;
# Follow the prompts!


Finally if you're particularly proficient with Linux or Networking (or both) you can opt to run your own hardware configured to your specifications. We don't directly provide support for vendors like Microtik, Unifi or others, but during the closed testing we've done in past, users have been able to set these vendor devices up and successfully connect. [https://github.com/CGHMN/config-examples Example configurations are available here] however are untested except by the user who submitted them. Please reach out to the committer for assistance if the configuration scripts do not work.

Once again, to clarify: CGHMN '''''does''''' '''''not specifically require using "real" vintage hardware''''' as doing so can be impractical for a number of reasons. A lot of users (including Cursed Silicon and others) use virtualization, particularly to run [[Services people are running|services on the network]] efficiently or to quickly test out applications and features. '''Connecting a modern computer (EG a Windows 10 or 11 PC) to the network while not disallowed will encounter a lot of issues due to the age of the servers and services it is communicating with and is discouraged'''</text>
    <sha1>975e1fdd249b04458abef9661685947e038d8475</sha1>
  </revision>
  <revision>
    <id>283</id>
    <parentid>282</parentid>
    <timestamp>2025-10-07T20:22:26Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Fixing formatting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4649" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
Compu-Global-Hyper-Mega-Net is now in '''''OPEN BETA!''''' That means if you're reading this, you've either filled out our signup page and gotten sent an email, or stumbled across this page on the Wiki. 


Either way, welcome!


So. To get ON Compu-Global-Hyper-Mega-Net (hereby referred to as CGHMN for easier reference) you'll need a few things.

# A retro computer/virtual machine or a device that can be ultimately terminated via ethernet. Using other networking standards like 802.11, Token Ring, AUI, BNC or others is totally fine, but you'll need to ultimately bridge them to Ethernet to talk to the device running Wireguard
# A device that can run the Wireguard and (optionally) Gretap protocols. Wireguard is a VPN stack that is used to encrypt traffic and connect your retro devices securely to the network over the internet. Gretap is used for tunneling "non TCP/IP" protocols, like IPX. Useful if you want to play DOOM or run other non-TCP/IP software, '''''but not required!'''''
# To '''have fun!''' Seriously. This project is meant to bring back the joy of the web as it existed in the 90's and 2000's. If you aren't having fun, we need to fix that.

For Step 2 you can use any kind of device that runs '''''Linux/BSD''''' such as a Raspberry Pi or others. Virtual Machines (such as Proxmox) are absolutely supported and encouraged! 


For users looking to connect physical machines, you will need a hardware device. We recommend something like the [https://www.gl-inet.com/products/gl-ar300m/ GL.iNet Shadow]. This device retails for around $30~ US dollars on retailers such as Amazon and can push 40 megabits of bandwidth to CGHMN over Wireguard. This is more than sufficient for a significant number of retro machines. This device has been deployed by Cursed Silicon and other users and has been successfully tested at-scale hosting 15 simultaneous users at the Seattle Interim Computer Festival retro computing event. 


Another option (if you have one) is the Raspberry Pi. Every Pi version through the original Pi 1 to the current Pi 5 [https://openwrt.org/toh/raspberry_pi_foundation/raspberry_pi is supported by OpenWRT]. Adding a cheap USB LAN adapter makes this an attractive option if you have a spare "old Ras Pi laying around" 


The third option is to run a virtual machine as your CGHMN gateway. We provide support primarily for '''''Proxmox''''' but other virtualization stacks such as VMware, Virtualbox and Hyper-V will work, but may require manual configuration by the user. '''This option is best suited for users wanting to run servers (websites, old game servers etc) as running old OSes in Proxmox comes with a significant graphics performance penalty'''  

We recommend running the [https://openwrt.org/ OpenWRT] router distribution regardless of which above option you choose. This supports an enormous array of hardware (including running as a VM) and even comes with a [https://cghmn.snep.zip/connect.sh ready-made script] written by our network architect, Snep. This script can be run on a device running OpenWRT to configure it directly for access to CGHMN.

Once installed in either a VM or on a physical device such as the GL.iNet Shadow, the device can be SSH'd into and the following commands can be run to begin configuration for CGHMN access.

# &lt;code&gt;wget &lt;nowiki&gt;https://cghmn.snep.zip/connect.sh&lt;/nowiki&gt;&lt;/code&gt;
# &lt;code&gt;ash setup-cghmn.sh&lt;/code&gt;
# Follow the prompts!


Finally if you're particularly proficient with Linux or Networking (or both) you can opt to run your own hardware configured to your specifications. We don't directly provide support for vendors like Microtik, Unifi or others, but during the closed testing we've done in past, users have been able to set these vendor devices up and successfully connect. [https://github.com/CGHMN/config-examples Example configurations are available here] however are untested except by the user who submitted them. Please reach out to the committer for assistance if the configuration scripts do not work.

Once again, to clarify: CGHMN '''''does''''' '''''not specifically require using "real" vintage hardware''''' as doing so can be impractical for a number of reasons. A lot of users (including Cursed Silicon and others) use virtualization, particularly to run [[Services people are running|services on the network]] efficiently or to quickly test out applications and features. '''Connecting a modern computer (EG a Windows 10 or 11 PC) to the network while not disallowed will encounter a lot of issues due to the age of the servers and services it is communicating with and is discouraged'''</text>
    <sha1>1d04ad6b29dd2cb99df633ea0ffdc76dc55dafa0</sha1>
  </revision>
  <revision>
    <id>284</id>
    <parentid>283</parentid>
    <timestamp>2025-10-07T20:24:08Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4771" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
Compu-Global-Hyper-Mega-Net is now in '''''OPEN BETA!''''' That means if you're reading this, you've either filled out our signup page and gotten sent an email, or stumbled across this page on the Wiki. 


Either way, welcome!


So. To get ON Compu-Global-Hyper-Mega-Net (hereby referred to as CGHMN for easier reference) you'll need a few things.

# A retro computer/virtual machine or a device that can be ultimately terminated via ethernet. Using other networking standards like 802.11, Token Ring, AUI, BNC or others is totally fine, but you'll need to ultimately bridge them to Ethernet to talk to the device running Wireguard
# A device that can run the Wireguard and (optionally) Gretap protocols. Wireguard is a VPN stack that is used to encrypt traffic and connect your retro devices securely to the network over the internet. Gretap is used for tunneling "non TCP/IP" protocols, like IPX. Useful if you want to play DOOM or run other non-TCP/IP software, '''''but not required!'''''
# To '''have fun!''' Seriously. This project is meant to bring back the joy of the web as it existed in the 90's and 2000's. If you aren't having fun, we need to fix that.

For Step 2 you can use any kind of device that runs '''''Linux/BSD''''' such as a Raspberry Pi or others. Virtual Machines (such as Proxmox) are absolutely supported and encouraged! 


For users looking to connect physical machines, you will need a hardware device. We recommend something like the [https://www.gl-inet.com/products/gl-ar300m/ GL.iNet Shadow]. This device retails for around $30~ US dollars on retailers such as Amazon and can push 40 megabits of bandwidth to CGHMN over Wireguard. This is more than sufficient for a significant number of retro machines. This device has been deployed by Cursed Silicon and other users and has been successfully tested at-scale hosting 15 simultaneous users at the Seattle Interim Computer Festival retro computing event. 


Another option (if you have one) is the Raspberry Pi. Every Pi version through the original Pi 1 to the current Pi 5 [https://openwrt.org/toh/raspberry_pi_foundation/raspberry_pi is supported by OpenWRT]. Adding a cheap USB LAN adapter makes this an attractive option if you have a spare "old Ras Pi laying around" 


The third option is to run a virtual machine as your CGHMN gateway. We provide support primarily for '''''Proxmox''''' but other virtualization stacks such as VMware, Virtualbox and Hyper-V will work, but may require manual configuration by the user. '''This option is best suited for users wanting to run servers (websites, old game servers etc) as running old OSes in Proxmox comes with a significant graphics performance penalty'''  

We recommend running the [https://openwrt.org/ OpenWRT] router distribution regardless of which above option you choose. This supports an enormous array of hardware (including running as a VM) and even comes with a [https://cghmn.snep.zip/connect.sh ready-made script] written by our network architect, Snep. This script can be run on a device running OpenWRT to configure it directly for access to CGHMN.

Once installed in either a VM or on a physical device such as the GL.iNet Shadow, the device can be SSH'd into and the following commands can be run to begin configuration for CGHMN access.

# &lt;code&gt;wget &lt;nowiki&gt;https://cghmn.snep.zip/connect.sh&lt;/nowiki&gt;&lt;/code&gt;
# &lt;code&gt;ash setup-cghmn.sh&lt;/code&gt;
# Follow the prompts
# [https://signup.cghmn.org/ Send us your Wireguard] '''Public Key''' on the signup page so we can add you to the network!


Finally if you're particularly proficient with Linux or Networking (or both) you can opt to run your own hardware configured to your specifications. We don't directly provide support for vendors like Microtik, Unifi or others, but during the closed testing we've done in past, users have been able to set these vendor devices up and successfully connect. [https://github.com/CGHMN/config-examples Example configurations are available here] however are untested except by the user who submitted them. Please reach out to the committer for assistance if the configuration scripts do not work.

Once again, to clarify: CGHMN '''''does''''' '''''not specifically require using "real" vintage hardware''''' as doing so can be impractical for a number of reasons. A lot of users (including Cursed Silicon and others) use virtualization, particularly to run [[Services people are running|services on the network]] efficiently or to quickly test out applications and features. '''Connecting a modern computer (EG a Windows 10 or 11 PC) to the network while not disallowed will encounter a lot of issues due to the age of the servers and services it is communicating with and is discouraged'''</text>
    <sha1>c41669b81a676ab1659d227d2db30f97b55fccbe</sha1>
  </revision>
  <revision>
    <id>285</id>
    <parentid>284</parentid>
    <timestamp>2025-10-07T20:50:22Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4794" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
Compu-Global-Hyper-Mega-Net is now in '''''OPEN BETA!''''' That means if you're reading this, you've either [https://signup.cghmn.org/ found our signup page], been sent an email, or just stumbled across this page on the Wiki. 


Either way, welcome!


So. To get ON Compu-Global-Hyper-Mega-Net (hereby referred to as CGHMN for easier reference) you'll need a few things.

# A retro computer/virtual machine or a device that can be ultimately terminated via ethernet. Using other networking standards like 802.11, Token Ring, AUI, BNC or others is totally fine, but you'll need to ultimately bridge them to Ethernet to talk to the device running Wireguard
# A device that can run the Wireguard and (optionally) Gretap protocols. Wireguard is a VPN stack that is used to encrypt traffic and connect your retro devices securely to the network over the internet. Gretap is used for tunneling "non TCP/IP" protocols, like IPX. Useful if you want to play DOOM or run other non-TCP/IP software, '''''but not required!'''''
# To '''have fun!''' Seriously. This project is meant to bring back the joy of the web as it existed in the 90's and 2000's. If you aren't having fun, we need to fix that.

For Step 2 you can use any kind of device that runs '''''Linux/BSD''''' such as a Raspberry Pi or others. Virtual Machines (such as Proxmox) are absolutely supported and encouraged! 


For users looking to connect physical machines, you will need a hardware device. We recommend something like the [https://www.gl-inet.com/products/gl-ar300m/ GL.iNet Shadow]. This device retails for around $30~ US dollars on retailers such as Amazon and can push 40 megabits of bandwidth to CGHMN over Wireguard. This is more than sufficient for a significant number of retro machines. This device has been deployed by Cursed Silicon and other users and has been successfully tested at-scale hosting 15 simultaneous users at the Seattle Interim Computer Festival retro computing event. 


Another option (if you have one) is the Raspberry Pi. Every Pi version through the original Pi 1 to the current Pi 5 [https://openwrt.org/toh/raspberry_pi_foundation/raspberry_pi is supported by OpenWRT]. Adding a cheap USB LAN adapter makes this an attractive option if you have a spare "old Ras Pi laying around" 


The third option is to run a virtual machine as your CGHMN gateway. We provide support primarily for '''''Proxmox''''' but other virtualization stacks such as VMware, Virtualbox and Hyper-V will work, but may require manual configuration by the user. '''This option is best suited for users wanting to run servers (websites, old game servers etc) as running old OSes in Proxmox comes with a significant graphics performance penalty'''  

We recommend running the [https://openwrt.org/ OpenWRT] router distribution regardless of which above option you choose. This supports an enormous array of hardware (including running as a VM) and even comes with a [https://cghmn.snep.zip/connect.sh ready-made script] written by our network architect, Snep. This script can be run on a device running OpenWRT to configure it directly for access to CGHMN.

Once installed in either a VM or on a physical device such as the GL.iNet Shadow, the device can be SSH'd into and the following commands can be run to begin configuration for CGHMN access.

# &lt;code&gt;wget &lt;nowiki&gt;https://cghmn.snep.zip/connect.sh&lt;/nowiki&gt;&lt;/code&gt;
# &lt;code&gt;ash setup-cghmn.sh&lt;/code&gt;
# Follow the prompts
# [https://signup.cghmn.org/ Send us your Wireguard] '''Public Key''' on the signup page so we can add you to the network!


Finally if you're particularly proficient with Linux or Networking (or both) you can opt to run your own hardware configured to your specifications. We don't directly provide support for vendors like Microtik, Unifi or others, but during the closed testing we've done in past, users have been able to set these vendor devices up and successfully connect. [https://github.com/CGHMN/config-examples Example configurations are available here] however are untested except by the user who submitted them. Please reach out to the committer for assistance if the configuration scripts do not work.

Once again, to clarify: CGHMN '''''does''''' '''''not specifically require using "real" vintage hardware''''' as doing so can be impractical for a number of reasons. A lot of users (including Cursed Silicon and others) use virtualization, particularly to run [[Services people are running|services on the network]] efficiently or to quickly test out applications and features. '''Connecting a modern computer (EG a Windows 10 or 11 PC) to the network while not disallowed will encounter a lot of issues due to the age of the servers and services it is communicating with and is discouraged'''</text>
    <sha1>4bbd44656cefe7bfbcd9d4f5b705e41adc8dc37d</sha1>
  </revision>
</page>
<page arvcontinue="20250816031124|259">
  <title>Compu-Global-Hyper-Mega-Net</title>
  <ns>0</ns>
  <id>61</id>
  <revision>
    <id>286</id>
    <parentid>167</parentid>
    <timestamp>2025-10-10T17:37:57Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Tweaked as we're in beta now</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4056" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
=== Preamble ===
Compu-Global-Hyper-Mega-Net (hereby shortened to '''''CGHMN''''' for easier reference) originally started as me making good on a promise to use a Cisco AS5300 I acquired years ago to make a Dial-Up internet provider. Over time while working on the project and watching other YouTubers work on their own ISP projects it became clear that many of them are happy to set up the hardware, there was very little interest (or ability) to make it usable to other folks, or to have anything fun or useful to "do" with it (beyond the novelty of browsing a few vintage websites such as FrogFinder)


CGHMN (its name [https://www.youtube.com/watch?v=9STeegpxSb0 borrowing from a Simpsons joke, naturally]) is another one of my "biting off far more than I can possibly chew" projects. Intended to be an intersection point between art, shitpost, rejection of "internet modernity", refuge for the nostalgic and a communal home for projects of a specifically retro computing bent.


CGHMN is currently in '''''[[Signup|Open Beta]]'''''. Users can sign up and join the network along with their devices. While the network is totally solid, we need a large enough userbase to make it interesting for users to contribute! A bit of a chicken-and-egg problem. But hopefully one we can overcome.


An eventual goal is to provide "open" access to an era of the web that has been not so much "lost" as ''obliterated'' by capitalism. A space that can mimic "the vibe" of the late 1990's internet through faithful reconstruction or mimicry of the hardware and software stacks that powered it.


Mechanisms will be implemented to discourage (but not outright prevent) "modern systems" from accessing the network where possible, both for the security of users on the network and to try and further the "vibe" of using period-accurate hardware and software. Using IRC and playing StarCraft on Windows 11 simply isn't as "''fun''" for us!
=== So what's this all about? ===


CGHMN is a collaborative project aimed to create a late 1990's/early 2000's compatible "internet" for retro computing enthusiasts and their machines to connect to each other

=== Okay so how do I connect to it ===


You can sign up '''[[Signup|right now]]!''' to "beta test" the network

===  How fast is it? ===


Total internal network capacity is '''''500Mbps''''' (symmetric). This is mainly due to the limitations of the OVH server being rented. This speed may be raised or lowered depending on future federation with other members. 

'''''Your''''' speed will likely depend on factors such as how fast your device can run Wireguard and your internet connection 

=== Is this safe to use? I thought connecting old PC's to the internet was a bad idea! ===


Compu-Global-Hyper-Mega-Net is not accessible by the wider internet and is specifically designed to be a ''hermetically sealed'' network. Users can only connect via the above methods '''and can only communicate with other devices on the network'''. Users that violate the Terms of Service or attempt to abuse the network (or other members) will have their access '''permanently removed'''. With that said the usual rules about not downloading suspicious files and other "internet hygiene" rules still apply. While we don't expect bad actors to be a problem, please ensure that any files contributed to the network are scanned for malware first! [https://www.virustotal.com/gui/home/upload VirusTotal] provides free scanning services for this.

=== How can I help? ===


A lot of folks have offered to donate server hosting which is wonderful. Though not (yet!) required. The two biggest things we need are 


'''Donations to buy infrastructure''' (Particularly hard disks!) there's an Amazon Wishlist here that will get updated over time. https://www.amazon.com/hz/wishlist/ls/1W3S0E9IN7ZB7?ref_=wl_share


'''Volunteers who want to set up services'''. Want to come build a website? Run an old game server? Have some weird retro hardware you want to attach to the network? Please, reach out!</text>
    <sha1>9b1bbf6d8c6f46dac3282e285850b5efd0c390d9</sha1>
  </revision>
</page>
<page arvcontinue="20250816031124|259">
  <title>How to Get Connected</title>
  <ns>0</ns>
  <id>82</id>
  <revision>
    <id>289</id>
    <parentid>218</parentid>
    <timestamp>2025-10-21T06:36:28Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>OPEN beta!</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11321" xml:space="preserve">[[Category:Compu-Global-Hyper-Mega-Net]]
This is a quick and dirty "how do I get on CGHMN" 

'''Since the service is in "open beta" these steps are a bit vague and manual. But over time as we figure out what works we'll add more connection methods and better documentation'''

=== Step 1: ===
[[Signup|'''Let us know you'd like to connect!''']] 

(We'll need information from you such as your Wireguard Pubkey to let you connect to the network)[[File:CGHMN.png|thumb|319x319px|Example CGHMN Router Setup using a GL-AR300M and basic network switch]]

=== Hardware requirements ===
To connect your retro machine(s) to the CGHMN, you'll need the following:
*'''An Ethernet connection on your retro device(s) of choice, with a TCP/IP (v4) stack for now! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works.'''

* '''Something with the ability to run Wireguard and forward IPv4 packets at the minimum and, for any non-IP packets, &lt;code&gt;gretap&lt;/code&gt; and &lt;code&gt;nftables&lt;/code&gt;. Personally we recommend something running OpenWRT, like the [https://www.gl-inet.com/products/gl-ar300m GL-AR300M] which we have successfully tested to work. We're currently working on a pre-built image for some select routers to make the setup easier for new members. A script to configure already existing OpenWRT instances can be found below.'''
* Alternatively, you can also run the CGHMN routing on any standard Linux box which has at least one Ethernet port and either a second one or WiFi for internet connectivity. &lt;s&gt;A basic script to set up a Linux machine as a router is posted below&lt;/s&gt; (TODO!).

* '''Optionally: A simple network switch, in case you want to add multiple machines to the network. You plug one end into the CGHMN Router box and then your clients can all access CGHMN. Super easy!'''

On the right is an example of what a CGHMN router setup could look like.

=== Get connected - With OpenWRT ===
If you chose to go with an OpenWRT compatible router or want to run OpenWRT on typical x86 hardware/in a VM, you can follow these steps to get yourself connected to the CGHMN:

# Update your OpenWRT install to the latest version to ensure all required packages are available and compatible.
# Download [https://raw.githubusercontent.com/jonasluehrig/cghmn-get-connected/refs/heads/main/openwrt/setup-cghmn.sh this script from GitHub] to your OpenWRT router: &lt;code&gt;wget https://cghmn.snep.zip/connect.sh&lt;/code&gt;
# Run the following commands on the router:
## &lt;code&gt;ash setup-cghmn.sh install-pkgs&lt;/code&gt;
## &lt;code&gt;ash setup-cghmn.sh init&lt;/code&gt;
## You will be asked what network port you'd like to use for the Retro LAN. This is where you will plug in your retro machines to be part of the CGHMN. Choose a port that is not assigned to any OpenWRT interface like '''lan''' or '''wan''' or which not already part of a bridge and enter the Linux interface name, e.g. &lt;code&gt;eth1&lt;/code&gt;, then press &lt;code&gt;[Enter]&lt;/code&gt; to continue. If your router only has two ports and you're using one for WAN, then you first have to [https://openwrt.org/docs/guide-user/luci/luci.secure#allow_access_from_internet enable the web UI and SSH access via the '''wan''' OpenWRT interface], remove the entire '''lan''' OpenWRT interface to free the network port and continue the setup over the IP address your router got on its WAN side. If you only have a single Ethernet port, you're running on a router setup we can't really recommend, however you can configure VLANs and use a managed switch to both get a WAN DHCP address for internet access and have a separate VLAN for the Retro LAN bridge over a single port. This is commonly referred to as "[[wikipedia:Router_on_a_stick|router on a stick]]". Just enter the VLAN interface name here if you choose to go that route.
# Now you will be given some information on the console, including a Wireguard public key. Send one of the CGHMN admins (currently CursedSilicon and Snep) that key so we can add your router to our Wireguard server. If you cannot copy-paste, for example, because you're on a VM VNC console, you can run &lt;code&gt;ash setup-cghmn.sh pubkey-qr&lt;/code&gt; to get a QR code printout of your public key, which can be scanned with a phone, tablet or software QR code parser to get the key as copy-pastable text.
# In return, you will receive a tunnel IPv4 address (&lt;code&gt;100.89.128.x/32&lt;/code&gt;) and a routed IPv4 subnet (&lt;code&gt;100.96.x.0/24&lt;/code&gt;) from us. These will be needed on the third and final step of the setup script:
## &lt;code&gt;ash setup-cghmn.sh set-tunnel-ip&lt;/code&gt;
# Once the script completed successfully, reboot the router to ensure all interfaces are up properly. After the reboot, your retro devices should receive an IP address in your routed IPv4 subnet on the Retro LAN port you chose above and be able to communicate with other machines on the CGHMN network.

=== Get Connected - Manually (Linux, Wireguard only, GRETAP follows shortly) ===
In case you want to setup a connection into the network manually, here are the required steps and information you should be needing:

* Generate a Wireguard private key and public key, this command writes a fresh Wireguard private key to &lt;code&gt;private-key&lt;/code&gt; and the corresponsing public key to &lt;code&gt;public-key&lt;/code&gt;:

 $ wg genkey | tee private-key | wg pubkey &gt; public-key

* NEVER share your private key, even with us! It should never be required outside of your own Wireguard setup!
* You will, however, need to share your public key with us. Send CursedSilicon or Snep on the Discord or via IRC a message including the public key and we'll add you to the tunnel.
* In return, you'll get two IP addresses from us: Your tunnel IP address, with which your router talks to our router, and a routed subnet, from which you can assign IPs to your own machines so they can talk to other CGHMN member devices on the network without NAT in the way.
* Next, you'll need to fill a Wireguard configuration file with the two IP addresses, like below:

 [Interface]
 PrivateKey = &lt;Your private key goes here&gt;
 Address = &lt;Your tunnel IP address goes here&gt;/32
 DNS = 100.89.128.0
 MTU = 1420
 
 [Peer]
 PublicKey = k/QiJIbMakMKgTCHVt8/D+8k4DzRVM6U33F3gMZfRUg=
 Endpoint = wg-admin.cursedsilicon.net:42070
 AllowedIPs = 172.23.0.0/16, 100.89.128.0/22, 100.96.0.0/13
 PersistentKeepalive = 15

* Save this file as &lt;code&gt;wg-cghmn.conf&lt;/code&gt;, for example.
* Then, run &lt;code&gt;wg-quick up ./wg-cghmn.conf&lt;/code&gt;, perhaps requiring &lt;code&gt;doas&lt;/code&gt;/&lt;code&gt;sudo&lt;/code&gt;, to bring the tunnel up and connect to the network!

This should bring whatever system you've set the tunnel up on onto the network and is now reachable for other members on the network, as long as the firewall on your device is congfigured accordingly, of course.

&lt;nowiki&gt;#&lt;/nowiki&gt;TODO: Add example of routed subnet configuration, perhaps on a different Wiki site

=== Get connected - Server Side, the Admins Guide ===
[[File:Example Configuration for new Wireguard Peer on Core Router.png|thumb|Example Configuration for new Wireguard Peer on Core Router]]
To get a member onto the network, they will send an admin of the project their randomly generated Wireguard key during the setup via the OpenWRT script. Here are the steps that admin will have to follow to get them up and running on the server side:

# Log in on the [https://router.core.cghmn:8443 Core Router] over an existing CGHMN network link
# Navigate to VPN -&gt; Wireguard -&gt; Peer Generator
# You will be asked to enter some data for the new peer, enter the following: 
## '''Instance:''' &lt;code&gt;WG_Member&lt;/code&gt;   
## '''Endpoint:''' &lt;code&gt;wg-admin.cursedsilicon.net:42070&lt;/code&gt;
## '''Name:''' &lt;code&gt;member.''&lt;Nickname of the new member&gt;''&lt;/code&gt;
## '''Public Key:''' &lt;code&gt;''&lt;their Wireguard public key they've sent over&gt;''&lt;/code&gt;
## '''Private Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Address:''' ''&lt;code&gt;&lt;Next highest IP from 100.89.128.0/22, this is their tunnel IP and is auto-filled&gt;&lt;/code&gt;''
## '''Pre-Shared Key:''' &lt;code&gt;''&lt;blank&gt;''&lt;/code&gt;
## '''Allowed IPs:''' &lt;code&gt;''&lt;the same as Address&gt;'', ''&lt;their routed subnet, [[How to Get Connected#But wait, what even is their routed subnet?|see below]]&gt;''&lt;/code&gt;
## '''Keepalive interval:''' ''&lt;code&gt;&lt;blank&gt;&lt;/code&gt;''
## '''DNS Servers:''' &lt;code&gt;''&lt;default value&gt;''&lt;/code&gt;
# Hit the "Store and generate next" button
# Navigate to VPN -&gt; Wireguard -&gt; Instances
# Hit the "Apply" button
# Do '''either one''' '''(not both!)''' of these steps, depending on if you can SSH into the GRETAP endpoint container:
## SSH into the CGHMN Proxmox Server and enter the command &lt;code&gt;pct enter 10403&lt;/code&gt;
## SSH directly into the GRETAP endpoint (formerly VXLAN endpoint) container with &lt;code&gt;ssh root@172.23.4.103&lt;/code&gt;
# From there, run the following command: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh &lt;member-tunnel-ip&gt; &lt;member-name&gt;&lt;/code&gt; where you replace &lt;code&gt;&lt;member-tunnel-ip&gt;&lt;/code&gt; with the IP tunnel address of the member as it was set above in the '''Address''' field, without the &lt;code&gt;/32&lt;/code&gt; CIDR subnet mask, and replace the &lt;code&gt;&lt;member-name&gt;&lt;/code&gt; with the same value you've entered above in the '''Name''' field. For example, like this: &lt;code&gt;bash /opt/vxlan-scripts/create-vxlan-interface.sh 100.89.128.6 member.snep.test&lt;/code&gt; This will create a GRETAP (and for legacy purposes, a VXLAN) interface and bring them up automagically. ''Ignore the fact it still says "VXLAN" everywhere, it does both.''
# Now you can send the member their Wireguard Tunnel IP and their routed subnet over and they can finish their client-side setup according to the mini-tutorial above.
# Rember to add the member and their tunnel and subnet IPs to the [[CGHMN-IP-Allocations|IP allocations page]] :)

==== But wait, what even ''is'' their routed subnet? ====
Each members routed subnet comes per default from the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IPv4 block and has a &lt;code&gt;/24&lt;/code&gt; mask. This subnet is their "Retro LAN", to which all their retro computers are hooked into via the router of their choosing. By default, NAT is enabled on the routers, so it wouldn't make a difference which subnet is used on the remote end for the retro machines. However, if someone wants to host servers in the CGHMN and doesn't want to do port forwading, they can disable NAT and let other membres directly connect to their machines via this routed subnet.

To get the routed subnet of a member, take the number from the last octet of the Wireguard tunnel IP of a member, say &lt;code&gt;100.89.128.'''6'''&lt;/code&gt;, and put it into the third octet of the &lt;code&gt;100.96.0.0/13&lt;/code&gt; IP block and replace the &lt;code&gt;/13&lt;/code&gt; with &lt;code&gt;/24&lt;/code&gt;, so you get &lt;code&gt;100.96.'''6'''.0/24&lt;/code&gt;. That is their routed subnet, simple as that!

=== After you get connected ===
There are a few optional things you might want to do.

==== Network mailing list ====
There is a mailing list you can subscribe to if you want to be notified about things that may affect CGHMN or core services. You can subscribe to the list here: https://berwick-upon-tweed.cobaltqu.be/postorius/lists/cghmn-announce.lists.cobaltqu.be/.


If you need to post to the list, you will need to subscribe before you can be added to the list of poster.

==== Explore things available on the network ====
There is a collection of [[services people are running]] - things like email/hosting/chat/search/etc.</text>
    <sha1>8f6269b0bcaf9a14a16a408f717b68cd5dd2f86b</sha1>
  </revision>
</page>
<page arvcontinue="20250816031124|259">
  <title>CGHMN NAT and Firewalls</title>
  <ns>0</ns>
  <id>95</id>
  <revision>
    <id>290</id>
    <timestamp>2025-10-26T06:25:41Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>Still a WIP but this is as much as I could write before sickness took over and I passed out</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3726" xml:space="preserve">[[Compu-Global-Hyper-Mega-Net|Compu-Global-Hyper-Mega-Net (CGHMN)]] exists in a difficult kind of space. We aim to emulate "the old web". A time of roughly 1995 to around 2005 or so. Before "Web 2.0" took off.

At time of writing that might not sound like too big a problem. After all, Windows 10 came out in 2015 and now it's 2025. But your 4th gen Core i7 PC is still perfectly usable. Just install Linux, right?

Unfortunately for us now we live at the end of history. In 1995 however the "World Wide Web" was in its infancy in such a way that every single year brought quantum technological leaps over the previous year. By the end of the millennium we'd gone from rudimentary analog Dial-Up services to Wireless Networking being accessible to consumers (Apple's AirPort routers alone showed up in 1999)

However on a technical level this began to create severe technical issues. The internet as it was originally designed assumed simple "end-to-end" connectivity. Every computer on the internet could (more or less) talk to another computer without exception.

This created two major problems.

The first one was IP exhaustion. Even by the 1990's there was an understanding that there simply wouldn't be enough IP addresses for everyone on the internet. This needed to be fixed, and fast! This lead to IPv6 as an evolutionary upgrade (a problem the internet still struggles to even deploy in 2025, despite being ratified in 1998)

The second, and much more obvious problem was security. By the year 2000 it was obviously apparent that every machine being able to talk to every other machine on Earth was a problem. Particularly when the dominant operating system these machines ran was what could be charitably described as..."not great" in terms of security. In the 2000's this would only escalate as the "[https://en.wikipedia.org/wiki/ILOVEYOU ILOVEYOU]" worm gave way to some of Windows XP's greatest hits, [https://en.wikipedia.org/wiki/Blaster_(computer_worm) Blaster], [https://en.wikipedia.org/wiki/Sasser_(computer_worm) Sasser], [https://en.wikipedia.org/wiki/Mydoom Mydoom], [https://en.wikipedia.org/wiki/Nimda Nimda] and [https://en.wikipedia.org/wiki/Conficker Conficker]. Among others.

A fortunate side-effect at the time of the explosive growth of computers on the internet was the institution of "Network Address Translation" or "NAT". In laymans terms this allows a bunch of computers to all sit behind a single IP address using a device such as a router. This technology is so ubiquitous that even in 2025 at time of writing it's still the defacto standard for computers and other devices to access the modern internet through. 

'''''However,''''' this technology came at a cost. The internet was originally predicated on the idea that every computer had its own, unique, IP address. NAT removed that assumption. And, in doing so, programs broke. Sometimes completely with services like FTP, sometimes in subtle ways. Like being unable to connect certain game players in a StarCraft lobby. 

The problem that NAT inadvertently introduced was that while "outbound" traffic would work fine. Such as you connecting to a website. If a program needed to receive data on your local computer, it could no longer simply sit and wait for a connection from a remote PC. An example would be AOL Instant Messenger (AIM). Chats between users are routed through a remote server. However to save on bandwidth, sending files happens directly between users. If user A is behind NAT. User B won't be able to "see" the computer and send data to it as desired.

The "solution" to this problem is known as '''''Port Forwarding'''''. You tell your router that [these ports] *always* go to "this PC on the LAN" exclusively.</text>
    <sha1>d6e6f6783be91a0fcb105b97e603becdb526a755</sha1>
  </revision>
  <revision>
    <id>291</id>
    <parentid>290</parentid>
    <timestamp>2025-10-26T22:42:51Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4078" xml:space="preserve">[[Compu-Global-Hyper-Mega-Net|Compu-Global-Hyper-Mega-Net (CGHMN)]] exists in a difficult kind of space. We aim to emulate "the old web". A time of roughly "1995 to around 2005 or so". Before "Web 2.0" took off. Though, really we support anything that speaks ethernet and (usually) TCP/IP. We've had devices as old as a DOS 286 PC clone connected successfully.


Unfortunately for us now we live at the end of history. In 1995 the "World Wide Web" was in its infancy in such a way that every single year brought quantum technological leaps over the previous year. By the end of the millennium we'd gone from rudimentary analog Dial-Up services to ''Wireless Networking'' being accessible to consumers (Apple's AirPort routers alone showed up in 1999)

However on a technical level this began to create severe issues. The internet as it was originally designed assumed simple "end-to-end" connectivity. Every computer on the internet could (more or less) talk to another computer without exception.


'''This created two major problems.'''

The first one was IP exhaustion. Even by the 1990's there was an understanding that there simply wouldn't be enough IP addresses for everyone on the internet. This needed to be fixed, and fast! This lead to IPv6 as an evolutionary upgrade (a problem the internet still struggles to even deploy in 2025, despite being ratified in 1998)


The second, and much more obvious problem was security. By the year 2000 it was obviously apparent that every machine being able to talk to every other machine on Earth was a problem. Particularly when the dominant operating system these machines ran was what could be charitably described as..."not great" in terms of security. In the 2000's this would only escalate as the "[[wikipedia:ILOVEYOU|ILOVEYOU]]" worm gave way to some of Windows XP's greatest hits, [[wikipedia:Blaster_(computer_worm)|Blaster]], [[wikipedia:Sasser_(computer_worm)|Sasser]], [[wikipedia:Mydoom|Mydoom]], [[wikipedia:Nimda|Nimda]] and [[wikipedia:Conficker|Conficker]]. Among others. 

A remedy proposed in the 1990's to the issue of IP exhaustion was "Network Address Translation" or "NAT". In layman terms this allows a bunch of computers to all sit behind a single IP address using a device such as a router. This technology is so ubiquitous that even in 2025 at time of writing it's still the defacto standard for home and business computers and other devices to access the modern internet.  

'''''However,''''' this technology came at a cost. The internet as most folks imagine (or remember it) was originally built on the idea that every computer had its own, unique, IP address. NAT broke that assumption. And, in doing so, programs broke. Sometimes completely with services like FTP, sometimes in subtle ways. Like being unable to connect certain game players in a StarCraft lobby. 


The problem that NAT introduced was that while "outbound" traffic would work fine. Such as you connecting to a website. If a program needed to ''receive'' data on your local computer, it could no longer simply sit and wait for a connection from a remote PC. An example would be AOL Instant Messenger (AIM). Chats between users are routed through a remote server. You and the Other User talk to a central server and it handles sending messages to-and-fro. ''However'' to save on bandwidth, sending files happens directly between users. If either user is behind NAT. They won't be able to "see" the remote computer and send data to it as desired.

The "solution" to this problem is known as '''''Port Forwarding'''''. You tell your router that [these ports] *always* go to [this IP address on the LAN] exclusively. This (mostly) solved the problem at the time. Additional solutions were proposed such as "UPnP" to allow programs to ask the router to forward ports for them dynamically. However, support for this was few-and-far-between (mostly BitTorrent clients) and in time it faded into oblivion. 


As stated before, we live at the end of history however. Which means we've got historical hindsight on the problems that existed</text>
    <sha1>d66e48767373856b44c6a40094b83cfe2e29e944</sha1>
  </revision>
  <revision>
    <id>292</id>
    <parentid>291</parentid>
    <timestamp>2025-10-26T22:57:10Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5176" xml:space="preserve">
== A brief history on how the internet worked in the 1990's ==
[[Compu-Global-Hyper-Mega-Net|Compu-Global-Hyper-Mega-Net (CGHMN)]] exists in a difficult kind of space. We aim to emulate "the old web". A time of roughly "1995 to around 2005 or so". A sort of nebulous "Before Web 2.0 took off" kind of period. Though, really we support anything that speaks ethernet and (usually) TCP/IP. We've had devices as old as a DOS 286 PC clone connected successfully. Most users trend toward Windows XP as their platform of choice due to its relative flexibility and widespread hardware and software support


Unfortunately for all of us we live at the "[[wikipedia:End_of_history|end of history]]". In 1995 the "World Wide Web" was in its infancy in such a way that every single year brought quantum technological leaps over the previous year. By the end of the millennium we'd gone from rudimentary analog Dial-Up services to ''Wireless Networking'' being accessible to consumers (Apple's AirPort routers alone showed up in 1999)

However on a technical level this began to create severe issues. The internet as it was originally designed assumed simple "end-to-end" connectivity. Every computer on the internet could (more or less) talk to another computer without exception.


'''This created two major problems.'''

The first one was IP exhaustion. Even by the 1990's there was an understanding that there simply wouldn't be enough IP addresses for everyone on the internet. This needed to be fixed, and fast! This lead to IPv6 as an evolutionary upgrade (a problem the internet still struggles to even deploy in 2025, despite being ratified in 1998)


The second, and much more obvious problem was security. By the year 2000 it was obviously apparent that every machine being able to talk to every other machine on Earth was a problem. Particularly when the dominant operating system these machines ran was what could be charitably described as..."not great" in terms of security. In the 2000's this would only escalate as the "[[wikipedia:ILOVEYOU|ILOVEYOU]]" worm gave way to some of Windows XP's greatest hits, [[wikipedia:Blaster_(computer_worm)|Blaster]], [[wikipedia:Sasser_(computer_worm)|Sasser]], [[wikipedia:Mydoom|Mydoom]], [[wikipedia:Nimda|Nimda]] and [[wikipedia:Conficker|Conficker]]. Among others. 

A remedy proposed in the 1990's to the issue of IP exhaustion was "Network Address Translation" or "NAT". In layman terms this allows a bunch of computers to all sit behind a single IP address using a device such as a router. This technology is so ubiquitous that even in 2025 at time of writing it's still the defacto standard for home and business computers and other devices to access the modern internet.  

'''''However,''''' this technology came at a cost. The internet as most folks imagine (or remember it) was originally built on the idea that every computer had its own, unique, IP address. NAT broke that assumption. And, in doing so, programs broke. Sometimes completely with services like FTP, sometimes in subtle ways. Like being unable to connect certain game players in a StarCraft lobby. 


The problem that NAT introduced was that while "outbound" traffic would work fine. Such as you connecting to a website. If a program needed to ''receive'' data on your local computer, it could no longer simply sit and wait for a connection from a remote PC. An example would be AOL Instant Messenger (AIM). Chats between users are routed through a remote server. You and the Other User talk to a central server and it handles sending messages to-and-fro. ''However'' to save on bandwidth, sending files happens directly between users. If either user is behind NAT. They won't be able to "see" the remote computer and send data to it as desired.

The "solution" to this problem is known as '''''Port Forwarding'''''. You tell your router that [these ports] *always* go to [this IP address on the LAN] exclusively. This (mostly) solved the problem at the time. Additional solutions were proposed such as "UPnP" to allow programs to ask the router to forward ports for them dynamically. However, support for this was few-and-far-between (mostly BitTorrent clients) and in time it faded into oblivion. 


As stated before, we live at the end of history. Which means we have the benefit of looking back on what was, and understanding the flaws. Which (finally) brings us to the point of this wiki page. 

== Okay but what does that have to do with CGHMN? ==
Every CGHMN user is allocated a /24 block of IP's. Effectively every user has 253 IP addresses to use as they'd like. This was a deliberate decision both to maximize the amount of freedom users would have to connect ALL their retro equipment if desired, and to try and allow direct end-to-end connectivity that the old web "expects"

'''''However''''' because we have the benefit of historical hindsight. Having directly allocated IP addresses does not mean that your devices are directly exposed to the network. By default (if using OpenWRT with Snep's setup script) your IP block will be ''firewalled'' against incoming connections. This is a necessary security measure because the very nature of the</text>
    <sha1>4872ea46e776ec6b907de63f7508580a07336767</sha1>
  </revision>
  <revision>
    <id>293</id>
    <parentid>292</parentid>
    <timestamp>2025-10-26T22:57:54Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5184" xml:space="preserve">


=== A brief history on how the internet worked in the 1990's ===
[[Compu-Global-Hyper-Mega-Net|Compu-Global-Hyper-Mega-Net (CGHMN)]] exists in a difficult kind of space. We aim to emulate "the old web". A time of roughly "1995 to around 2005 or so". A sort of nebulous "Before Web 2.0 took off" kind of period. Though, really we support anything that speaks ethernet and (usually) TCP/IP. We've had devices as old as a DOS 286 PC clone connected successfully. Most users trend toward Windows XP as their platform of choice due to its relative flexibility and widespread hardware and software support


Unfortunately for all of us we live at the "[[wikipedia:End_of_history|end of history]]". In 1995 the "World Wide Web" was in its infancy in such a way that every single year brought quantum technological leaps over the previous year. By the end of the millennium we'd gone from rudimentary analog Dial-Up services to ''Wireless Networking'' being accessible to consumers (Apple's AirPort routers alone showed up in 1999)

However on a technical level this began to create severe issues. The internet as it was originally designed assumed simple "end-to-end" connectivity. Every computer on the internet could (more or less) talk to another computer without exception.


'''This created two major problems.'''

The first one was IP exhaustion. Even by the 1990's there was an understanding that there simply wouldn't be enough IP addresses for everyone on the internet. This needed to be fixed, and fast! This lead to IPv6 as an evolutionary upgrade (a problem the internet still struggles to even deploy in 2025, despite being ratified in 1998)


The second, and much more obvious problem was security. By the year 2000 it was obviously apparent that every machine being able to talk to every other machine on Earth was a problem. Particularly when the dominant operating system these machines ran was what could be charitably described as..."not great" in terms of security. In the 2000's this would only escalate as the "[[wikipedia:ILOVEYOU|ILOVEYOU]]" worm gave way to some of Windows XP's greatest hits, [[wikipedia:Blaster_(computer_worm)|Blaster]], [[wikipedia:Sasser_(computer_worm)|Sasser]], [[wikipedia:Mydoom|Mydoom]], [[wikipedia:Nimda|Nimda]] and [[wikipedia:Conficker|Conficker]]. Among others. 

A remedy proposed in the 1990's to the issue of IP exhaustion was "Network Address Translation" or "NAT". In layman terms this allows a bunch of computers to all sit behind a single IP address using a device such as a router. This technology is so ubiquitous that even in 2025 at time of writing it's still the defacto standard for home and business computers and other devices to access the modern internet.  

'''''However,''''' this technology came at a cost. The internet as most folks imagine (or remember it) was originally built on the idea that every computer had its own, unique, IP address. NAT broke that assumption. And, in doing so, programs broke. Sometimes completely with services like FTP, sometimes in subtle ways. Like being unable to connect certain game players in a StarCraft lobby. 


The problem that NAT introduced was that while "outbound" traffic would work fine. Such as you connecting to a website. If a program needed to ''receive'' data on your local computer, it could no longer simply sit and wait for a connection from a remote PC. An example would be AOL Instant Messenger (AIM). Chats between users are routed through a remote server. You and the Other User talk to a central server and it handles sending messages to-and-fro. ''However'' to save on bandwidth, sending files happens directly between users. If either user is behind NAT. They won't be able to "see" the remote computer and send data to it as desired.

The "solution" to this problem is known as '''''Port Forwarding'''''. You tell your router that [these ports] *always* go to [this IP address on the LAN] exclusively. This (mostly) solved the problem at the time. Additional solutions were proposed such as "UPnP" to allow programs to ask the router to forward ports for them dynamically. However, support for this was few-and-far-between (mostly BitTorrent clients) and in time it faded into oblivion. 


As stated before, we live at the end of history. Which means we have the benefit of looking back on what was, and understanding the flaws. Which (finally) brings us to the point of this wiki page. 

==== Okay but what does that have to do with CGHMN? ====
Every CGHMN user is allocated a /24 block of IP's. Effectively every user has 253 IP addresses to use as they'd like. This was a deliberate decision both to maximize the amount of freedom users would have to connect ALL their retro equipment if desired, and to try and allow direct end-to-end connectivity that the old web "expects"

'''''However''''' because we have the benefit of historical hindsight. Having directly allocated IP addresses does not mean that your devices are directly exposed to the network. By default (if using OpenWRT with Snep's setup script) your IP block will be ''firewalled'' against incoming connections. This is a necessary security measure because the very nature of the</text>
    <sha1>1dbe5c99f13caf6b2639fc88e8726e2af91ca8b9</sha1>
  </revision>
  <revision>
    <id>294</id>
    <parentid>293</parentid>
    <timestamp>2025-10-26T23:00:08Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <comment>/* A brief history on how the internet worked in the 1990's */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5256" xml:space="preserve">


=== A brief history on how the internet worked in the 1990's ===
[[Compu-Global-Hyper-Mega-Net|Compu-Global-Hyper-Mega-Net (CGHMN)]] exists in a difficult kind of space. We aim to emulate "the old web". A time of roughly "1995 to around 2005 or so". A sort of nebulous "Before Web 2.0 took off" kind of period. Though, really we support anything that speaks ethernet and (usually) TCP/IP. We've had devices as old as a DOS 286 PC clone connected successfully. Most users trend toward Windows XP as their platform of choice due to its relative flexibility and widespread hardware and software support


Unfortunately for all of us we live at the "[[wikipedia:End_of_history|end of history]]". In 1995 the "World Wide Web" was in its infancy in such a way that every single year brought quantum technological leaps over the previous year. By the end of the millennium we'd gone from rudimentary analog Dial-Up services to ''Wireless Networking'' being accessible to consumers (Apple's AirPort routers alone showed up in 1999)

However on a technical level this began to create severe issues. The internet as it was originally designed assumed simple "end-to-end" connectivity. Every computer on the internet could (more or less) talk to another computer without exception.


'''This created two major problems.'''

The first one was IP exhaustion. Even by the 1990's there was an understanding that there simply wouldn't be enough IP addresses for everyone on the internet. This needed to be fixed, and fast! This lead to IPv6 as an evolutionary upgrade (a problem the internet still struggles to even deploy in 2025, despite being ratified in 1998)


The second, and much more obvious problem was security. By the year 2000 it was obviously apparent that every machine being able to talk to every other machine on Earth was a problem. Particularly when the dominant operating system these machines ran was what could be charitably described as..."not great" in terms of security. In the 2000's this would only escalate as the "[[wikipedia:ILOVEYOU|ILOVEYOU]]" worm gave way to some of Windows XP's greatest hits, [[wikipedia:Blaster_(computer_worm)|Blaster]], [[wikipedia:Sasser_(computer_worm)|Sasser]], [[wikipedia:Mydoom|Mydoom]], [[wikipedia:Nimda|Nimda]] and [[wikipedia:Conficker|Conficker]]. Among others. 

A remedy proposed in the 1990's to the issue of IP exhaustion was "Network Address Translation" or "NAT". In layman terms this allows a bunch of computers to all sit behind a single IP address using a device such as a router. This technology is so ubiquitous that even in 2025 at time of writing it's still the defacto standard for home and business computers and other devices to access the modern internet.  

'''''However,''''' this technology came at a cost. The internet as most folks imagine (or remember it) was originally built on the idea that every computer had its own, unique, IP address. NAT broke that assumption. And, in doing so, programs broke. Sometimes completely with services like FTP, sometimes in subtle ways. Like being unable to connect certain game players in a StarCraft lobby. 


The problem that NAT introduced was that while "outbound" traffic would work fine. Such as you connecting to a website. If a program needed to ''receive'' data on your local computer, it could no longer simply sit and wait for a connection from a remote PC. An example would be AOL Instant Messenger (AIM). Chats between users are routed through a remote server. You and the Other User talk to a central server and it handles sending messages to-and-fro. ''However'' to save on bandwidth, sending files happens directly between users. If either user is behind NAT. They won't be able to "see" the remote computer and send data to it as desired.

The "solution" to this problem is known as '''''Port Forwarding'''''. You tell your router that [these ports] *always* go to [this IP address on the LAN] exclusively. This (mostly) solved the problem at the time. Additional solutions were proposed such as "UPnP" to allow programs to ask the router to forward ports for them dynamically. However, support for this was few-and-far-between (mostly BitTorrent clients) and in time it faded into oblivion. 


As stated before, we live at the end of history. Which means we have the benefit of looking back on what was, and understanding the flaws. Which (finally) brings us to the point of this wiki page. 

=== Okay but what does that have to do with CGHMN? ===
Every CGHMN user is allocated a /24 block of IP's. Effectively every user has 253 IP addresses to use as they'd like. This was a deliberate decision both to maximize the amount of freedom users would have to connect ALL their retro equipment if desired, and to try and allow direct end-to-end connectivity that the old web "expects"

'''''However''''' because we have the benefit of historical hindsight. Having directly allocated IP addresses does not mean that your devices are directly exposed to the network. By default (if using OpenWRT with Snep's setup script) your IP block will be ''firewalled'' against incoming connections. This is a necessary security measure because the very nature of the

=== So, what stuff breaks, exactly? ===

=== How do I opt-out out? ===</text>
    <sha1>dab03d5ff840ea15616708fc15000848e80536e8</sha1>
  </revision>
  <revision>
    <id>295</id>
    <parentid>294</parentid>
    <timestamp>2025-10-26T23:16:08Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7857" xml:space="preserve">


=== A brief history on how the internet worked in the 1990's ===
[[Compu-Global-Hyper-Mega-Net|Compu-Global-Hyper-Mega-Net (CGHMN)]] exists in a difficult kind of space. We aim to emulate "the old web". A time of roughly "1995 to around 2005 or so". A sort of nebulous "Before Web 2.0 took off" kind of period. Though, really we support anything that speaks ethernet and (usually) TCP/IP. We've had devices as old as a DOS 286 PC clone connected successfully. Most users trend toward Windows XP as their platform of choice due to its relative flexibility and widespread hardware and software support


Unfortunately for all of us we live at the "[[wikipedia:End_of_history|end of history]]". In 1995 the "World Wide Web" was in its infancy in such a way that every single year brought quantum technological leaps over the previous year. By the end of the millennium we'd gone from rudimentary analog Dial-Up services to ''Wireless Networking'' being accessible to consumers (Apple's AirPort routers alone showed up in 1999)

However on a technical level this began to create severe issues. The internet as it was originally designed assumed simple "end-to-end" connectivity. Every computer on the internet could (more or less) talk to another computer without exception.


&lt;big&gt;'''This created two major problems:'''&lt;/big&gt;

The first one was IP exhaustion. Even by the 1990's there was an understanding that there simply wouldn't be enough IP addresses for everyone on the internet. This needed to be fixed, and fast! This lead to IPv6 as an evolutionary upgrade (a problem the internet still struggles to even deploy in 2025, despite being ratified in 1998)


The second, and much more obvious problem was security. By the year 2000 it was obviously apparent that every machine being able to talk to every other machine on Earth was a problem. Particularly when the dominant operating system these machines ran was what could be charitably described as..."not great" in terms of security. In the 2000's this would only escalate as the "[[wikipedia:ILOVEYOU|ILOVEYOU]]" worm gave way to some of Windows XP's greatest hits, [[wikipedia:Blaster_(computer_worm)|Blaster]], [[wikipedia:Sasser_(computer_worm)|Sasser]], [[wikipedia:Mydoom|Mydoom]], [[wikipedia:Nimda|Nimda]] and [[wikipedia:Conficker|Conficker]]. Among others. 

A remedy proposed in the 1990's to the issue of IP exhaustion was "Network Address Translation" or "NAT". In layman terms this allows a bunch of computers to all sit behind a single IP address using a device such as a router. This technology is so ubiquitous that even in 2025 at time of writing it's still the defacto standard for home and business computers and other devices to access the modern internet.  

'''''However,''''' this technology came at a cost. The internet as most folks imagine (or remember it) was originally built on the idea that every computer had its own, unique, IP address. NAT broke that assumption. And, in doing so, programs broke. Sometimes completely with services like FTP, sometimes in subtle ways. Like being unable to connect certain game players in a StarCraft lobby. 


The problem that NAT introduced was that while "outbound" traffic would work fine. Such as you connecting to a website. If a program needed to ''receive'' data on your local computer, it could no longer simply sit and wait for a connection from a remote PC. An example would be AOL Instant Messenger (AIM). Chats between users are routed through a remote server. You and the Other User talk to a central server and it handles sending messages to-and-fro. ''However'' to save on bandwidth, sending files happens directly between users. If either user is behind NAT. They won't be able to "see" the remote computer and send data to it as desired.

The "solution" to this problem is known as '''''Port Forwarding'''''. You tell your router that [these ports] *always* go to [this IP address on the LAN] exclusively. This (mostly) solved the problem at the time. Additional solutions were proposed such as "UPnP" to allow programs to ask the router to forward ports for them dynamically. However, support for this was few-and-far-between (mostly BitTorrent clients) and in time it faded into oblivion. 


As stated before, we live at the end of history. Which means we have the benefit of looking back on what was, and understanding the flaws. Which (finally) brings us to the point of this wiki page. 

=== Okay but what does that have to do with CGHMN? ===
Every CGHMN user is allocated a /24 block of IP's. Effectively every user has 253 IP addresses to use as they'd like. This was a deliberate decision both to maximize the amount of freedom users would have to connect ALL their retro equipment if desired, and to try and allow direct end-to-end connectivity that the old web "expects"

'''''However''''' because we have the benefit of historical hindsight. Having directly allocated IP addresses does not mean that your devices are directly exposed to the network. By default (if using OpenWRT with Snep's setup script) your IP block will be ''firewalled'' against incoming connections. This is a necessary security measure because the very nature of the

=== So, what stuff breaks, exactly? ===

There's no definitive list of "what" breaks under this decision. A broad (but by no means encompassing) list of things that ''won't work'' are

- Servers. You won't be able to run any kind of server or service (EG: hosting your own website, running a game server) without the ability for users to connect to it

- Games that '''''don't''''' use a server browser. Games like Quake or Halo where users all connect to a single server to play on will work (provided the server is either port forwarded or the firewall is disabled) but other games such as StarCraft or Command &amp; Conquer have players connect dynamically connect to a single player as the "host" (typically the player that created the game lobby). These will not work

- FTP! FTP is such an old protocol that the '''''remote server''''' initiates a connection back to the client and then begins sending files that way. This was fixed in [https://datatracker.ietf.org/doc/html/rfc1579 RFC 1579] with the "Firewall-Friendly FTP" proposal. Unfortunately despite being proposed in February 1994, some software such as Microsoft FrontPage did not enable it until 2003(!)

- AIM file transfers. As described already on this wiki page, AIM (and IRC and other chat clients such as MSN or Yahoo) all use a direct connection between two computers to send files across a network


=== How do I opt-out out? ===
&lt;br&gt;

&lt;br&gt;

&lt;big&gt;'''It should be made completely clear that opting out of using the OpenWRT firewall is not a decision that should be made lightly. We cannot explicitly guarantee that a user won't accidentally (or intentionally) release a malware Pandora's Box on the network. Blaster/Sasser/Mydoom/ILOVEYOU/etc are still real malware samples that can be downloaded and executed either by mistake or by a malicious user. We highly recommend installing any and all software patches that were (or are) available for your chosen systems before doing this!'''&lt;/big&gt;

There are two "modes" of opt-out available. Depending on user preference. 

The most drastic is simply to disable OpenWRT's firewall completely. This means any machine you plug in will have direct access to the network and any other devices on the network will be able to directly access it. If you choose this option we highly recommend putting any machines behind a (preferably modern!) Firewall and then port forwarding as necessary 

The other option is to set a static (fixed) IP address on the device you want to run servers or play games from. Once this is done you can access the OpenWRT Firewall page (Network -&gt; Firewall) and manually forward the required ports for that specific host.</text>
    <sha1>fced1f991d1cdfb3ca970827261b32391f46b792</sha1>
  </revision>
  <revision>
    <id>296</id>
    <parentid>295</parentid>
    <timestamp>2025-10-26T23:16:47Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7904" xml:space="preserve">= Or "a treatise on setting up a retro network" =


=== A brief history on how the internet worked in the 1990's ===
[[Compu-Global-Hyper-Mega-Net|Compu-Global-Hyper-Mega-Net (CGHMN)]] exists in a difficult kind of space. We aim to emulate "the old web". A time of roughly "1995 to around 2005 or so". A sort of nebulous "Before Web 2.0 took off" kind of period. Though, really we support anything that speaks ethernet and (usually) TCP/IP. We've had devices as old as a DOS 286 PC clone connected successfully. Most users trend toward Windows XP as their platform of choice due to its relative flexibility and widespread hardware and software support


Unfortunately for all of us we live at the "[[wikipedia:End_of_history|end of history]]". In 1995 the "World Wide Web" was in its infancy in such a way that every single year brought quantum technological leaps over the previous year. By the end of the millennium we'd gone from rudimentary analog Dial-Up services to ''Wireless Networking'' being accessible to consumers (Apple's AirPort routers alone showed up in 1999)

However on a technical level this began to create severe issues. The internet as it was originally designed assumed simple "end-to-end" connectivity. Every computer on the internet could (more or less) talk to another computer without exception.


&lt;big&gt;'''This created two major problems:'''&lt;/big&gt;

The first one was IP exhaustion. Even by the 1990's there was an understanding that there simply wouldn't be enough IP addresses for everyone on the internet. This needed to be fixed, and fast! This lead to IPv6 as an evolutionary upgrade (a problem the internet still struggles to even deploy in 2025, despite being ratified in 1998)


The second, and much more obvious problem was security. By the year 2000 it was obviously apparent that every machine being able to talk to every other machine on Earth was a problem. Particularly when the dominant operating system these machines ran was what could be charitably described as..."not great" in terms of security. In the 2000's this would only escalate as the "[[wikipedia:ILOVEYOU|ILOVEYOU]]" worm gave way to some of Windows XP's greatest hits, [[wikipedia:Blaster_(computer_worm)|Blaster]], [[wikipedia:Sasser_(computer_worm)|Sasser]], [[wikipedia:Mydoom|Mydoom]], [[wikipedia:Nimda|Nimda]] and [[wikipedia:Conficker|Conficker]]. Among others. 

A remedy proposed in the 1990's to the issue of IP exhaustion was "Network Address Translation" or "NAT". In layman terms this allows a bunch of computers to all sit behind a single IP address using a device such as a router. This technology is so ubiquitous that even in 2025 at time of writing it's still the defacto standard for home and business computers and other devices to access the modern internet.  

'''''However,''''' this technology came at a cost. The internet as most folks imagine (or remember it) was originally built on the idea that every computer had its own, unique, IP address. NAT broke that assumption. And, in doing so, programs broke. Sometimes completely with services like FTP, sometimes in subtle ways. Like being unable to connect certain game players in a StarCraft lobby. 


The problem that NAT introduced was that while "outbound" traffic would work fine. Such as you connecting to a website. If a program needed to ''receive'' data on your local computer, it could no longer simply sit and wait for a connection from a remote PC. An example would be AOL Instant Messenger (AIM). Chats between users are routed through a remote server. You and the Other User talk to a central server and it handles sending messages to-and-fro. ''However'' to save on bandwidth, sending files happens directly between users. If either user is behind NAT. They won't be able to "see" the remote computer and send data to it as desired.

The "solution" to this problem is known as '''''Port Forwarding'''''. You tell your router that [these ports] *always* go to [this IP address on the LAN] exclusively. This (mostly) solved the problem at the time. Additional solutions were proposed such as "UPnP" to allow programs to ask the router to forward ports for them dynamically. However, support for this was few-and-far-between (mostly BitTorrent clients) and in time it faded into oblivion. 


As stated before, we live at the end of history. Which means we have the benefit of looking back on what was, and understanding the flaws. Which (finally) brings us to the point of this wiki page. 

=== Okay but what does that have to do with CGHMN? ===
Every CGHMN user is allocated a /24 block of IP's. Effectively every user has 253 IP addresses to use as they'd like. This was a deliberate decision both to maximize the amount of freedom users would have to connect ALL their retro equipment if desired, and to try and allow direct end-to-end connectivity that the old web "expects"

'''''However''''' because we have the benefit of historical hindsight. Having directly allocated IP addresses does not mean that your devices are directly exposed to the network. By default (if using OpenWRT with Snep's setup script) your IP block will be ''firewalled'' against incoming connections. This is a necessary security measure because the very nature of the

=== So, what stuff breaks, exactly? ===

There's no definitive list of "what" breaks under this decision. A broad (but by no means encompassing) list of things that ''won't work'' are

- Servers. You won't be able to run any kind of server or service (EG: hosting your own website, running a game server) without the ability for users to connect to it

- Games that '''''don't''''' use a server browser. Games like Quake or Halo where users all connect to a single server to play on will work (provided the server is either port forwarded or the firewall is disabled) but other games such as StarCraft or Command &amp; Conquer have players connect dynamically connect to a single player as the "host" (typically the player that created the game lobby). These will not work

- FTP! FTP is such an old protocol that the '''''remote server''''' initiates a connection back to the client and then begins sending files that way. This was fixed in [https://datatracker.ietf.org/doc/html/rfc1579 RFC 1579] with the "Firewall-Friendly FTP" proposal. Unfortunately despite being proposed in February 1994, some software such as Microsoft FrontPage did not enable it until 2003(!)

- AIM file transfers. As described already on this wiki page, AIM (and IRC and other chat clients such as MSN or Yahoo) all use a direct connection between two computers to send files across a network


=== How do I opt-out out? ===
&lt;br&gt;

&lt;br&gt;

&lt;big&gt;'''It should be made completely clear that opting out of using the OpenWRT firewall is not a decision that should be made lightly. We cannot explicitly guarantee that a user won't accidentally (or intentionally) release a malware Pandora's Box on the network. Blaster/Sasser/Mydoom/ILOVEYOU/etc are still real malware samples that can be downloaded and executed either by mistake or by a malicious user. We highly recommend installing any and all software patches that were (or are) available for your chosen systems before doing this!'''&lt;/big&gt;

There are two "modes" of opt-out available. Depending on user preference. 

The most drastic is simply to disable OpenWRT's firewall completely. This means any machine you plug in will have direct access to the network and any other devices on the network will be able to directly access it. If you choose this option we highly recommend putting any machines behind a (preferably modern!) Firewall and then port forwarding as necessary 

The other option is to set a static (fixed) IP address on the device you want to run servers or play games from. Once this is done you can access the OpenWRT Firewall page (Network -&gt; Firewall) and manually forward the required ports for that specific host.</text>
    <sha1>339616b75bd7c426a85f1e5b4e956d8cf22fdc0d</sha1>
  </revision>
  <revision>
    <id>297</id>
    <parentid>296</parentid>
    <timestamp>2025-10-26T23:17:15Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7854" xml:space="preserve">=== A brief history on how the internet worked in the 1990's ===

[[Compu-Global-Hyper-Mega-Net|Compu-Global-Hyper-Mega-Net (CGHMN)]] exists in a difficult kind of space. We aim to emulate "the old web". A time of roughly "1995 to around 2005 or so". A sort of nebulous "Before Web 2.0 took off" kind of period. Though, really we support anything that speaks ethernet and (usually) TCP/IP. We've had devices as old as a DOS 286 PC clone connected successfully. Most users trend toward Windows XP as their platform of choice due to its relative flexibility and widespread hardware and software support


Unfortunately for all of us we live at the "[[wikipedia:End_of_history|end of history]]". In 1995 the "World Wide Web" was in its infancy in such a way that every single year brought quantum technological leaps over the previous year. By the end of the millennium we'd gone from rudimentary analog Dial-Up services to ''Wireless Networking'' being accessible to consumers (Apple's AirPort routers alone showed up in 1999)

However on a technical level this began to create severe issues. The internet as it was originally designed assumed simple "end-to-end" connectivity. Every computer on the internet could (more or less) talk to another computer without exception.


&lt;big&gt;'''This created two major problems:'''&lt;/big&gt;

The first one was IP exhaustion. Even by the 1990's there was an understanding that there simply wouldn't be enough IP addresses for everyone on the internet. This needed to be fixed, and fast! This lead to IPv6 as an evolutionary upgrade (a problem the internet still struggles to even deploy in 2025, despite being ratified in 1998)


The second, and much more obvious problem was security. By the year 2000 it was obviously apparent that every machine being able to talk to every other machine on Earth was a problem. Particularly when the dominant operating system these machines ran was what could be charitably described as..."not great" in terms of security. In the 2000's this would only escalate as the "[[wikipedia:ILOVEYOU|ILOVEYOU]]" worm gave way to some of Windows XP's greatest hits, [[wikipedia:Blaster_(computer_worm)|Blaster]], [[wikipedia:Sasser_(computer_worm)|Sasser]], [[wikipedia:Mydoom|Mydoom]], [[wikipedia:Nimda|Nimda]] and [[wikipedia:Conficker|Conficker]]. Among others. 

A remedy proposed in the 1990's to the issue of IP exhaustion was "Network Address Translation" or "NAT". In layman terms this allows a bunch of computers to all sit behind a single IP address using a device such as a router. This technology is so ubiquitous that even in 2025 at time of writing it's still the defacto standard for home and business computers and other devices to access the modern internet.  

'''''However,''''' this technology came at a cost. The internet as most folks imagine (or remember it) was originally built on the idea that every computer had its own, unique, IP address. NAT broke that assumption. And, in doing so, programs broke. Sometimes completely with services like FTP, sometimes in subtle ways. Like being unable to connect certain game players in a StarCraft lobby. 


The problem that NAT introduced was that while "outbound" traffic would work fine. Such as you connecting to a website. If a program needed to ''receive'' data on your local computer, it could no longer simply sit and wait for a connection from a remote PC. An example would be AOL Instant Messenger (AIM). Chats between users are routed through a remote server. You and the Other User talk to a central server and it handles sending messages to-and-fro. ''However'' to save on bandwidth, sending files happens directly between users. If either user is behind NAT. They won't be able to "see" the remote computer and send data to it as desired.

The "solution" to this problem is known as '''''Port Forwarding'''''. You tell your router that [these ports] *always* go to [this IP address on the LAN] exclusively. This (mostly) solved the problem at the time. Additional solutions were proposed such as "UPnP" to allow programs to ask the router to forward ports for them dynamically. However, support for this was few-and-far-between (mostly BitTorrent clients) and in time it faded into oblivion. 


As stated before, we live at the end of history. Which means we have the benefit of looking back on what was, and understanding the flaws. Which (finally) brings us to the point of this wiki page. 

=== Okay but what does that have to do with CGHMN? ===
Every CGHMN user is allocated a /24 block of IP's. Effectively every user has 253 IP addresses to use as they'd like. This was a deliberate decision both to maximize the amount of freedom users would have to connect ALL their retro equipment if desired, and to try and allow direct end-to-end connectivity that the old web "expects"

'''''However''''' because we have the benefit of historical hindsight. Having directly allocated IP addresses does not mean that your devices are directly exposed to the network. By default (if using OpenWRT with Snep's setup script) your IP block will be ''firewalled'' against incoming connections. This is a necessary security measure because the very nature of the

=== So, what stuff breaks, exactly? ===

There's no definitive list of "what" breaks under this decision. A broad (but by no means encompassing) list of things that ''won't work'' are

- Servers. You won't be able to run any kind of server or service (EG: hosting your own website, running a game server) without the ability for users to connect to it

- Games that '''''don't''''' use a server browser. Games like Quake or Halo where users all connect to a single server to play on will work (provided the server is either port forwarded or the firewall is disabled) but other games such as StarCraft or Command &amp; Conquer have players connect dynamically connect to a single player as the "host" (typically the player that created the game lobby). These will not work

- FTP! FTP is such an old protocol that the '''''remote server''''' initiates a connection back to the client and then begins sending files that way. This was fixed in [https://datatracker.ietf.org/doc/html/rfc1579 RFC 1579] with the "Firewall-Friendly FTP" proposal. Unfortunately despite being proposed in February 1994, some software such as Microsoft FrontPage did not enable it until 2003(!)

- AIM file transfers. As described already on this wiki page, AIM (and IRC and other chat clients such as MSN or Yahoo) all use a direct connection between two computers to send files across a network


=== How do I opt-out out? ===
&lt;br&gt;

&lt;br&gt;

&lt;big&gt;'''It should be made completely clear that opting out of using the OpenWRT firewall is not a decision that should be made lightly. We cannot explicitly guarantee that a user won't accidentally (or intentionally) release a malware Pandora's Box on the network. Blaster/Sasser/Mydoom/ILOVEYOU/etc are still real malware samples that can be downloaded and executed either by mistake or by a malicious user. We highly recommend installing any and all software patches that were (or are) available for your chosen systems before doing this!'''&lt;/big&gt;

There are two "modes" of opt-out available. Depending on user preference. 

The most drastic is simply to disable OpenWRT's firewall completely. This means any machine you plug in will have direct access to the network and any other devices on the network will be able to directly access it. If you choose this option we highly recommend putting any machines behind a (preferably modern!) Firewall and then port forwarding as necessary 

The other option is to set a static (fixed) IP address on the device you want to run servers or play games from. Once this is done you can access the OpenWRT Firewall page (Network -&gt; Firewall) and manually forward the required ports for that specific host.</text>
    <sha1>06a4bf66b506a982bd7cf8e4ff8531c44a037087</sha1>
  </revision>
  <revision>
    <id>298</id>
    <parentid>297</parentid>
    <timestamp>2025-10-26T23:36:29Z</timestamp>
    <contributor>
      <username>CursedSilicon</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8056" xml:space="preserve">=== A brief history on how the internet worked in the 1990's ===

[[Compu-Global-Hyper-Mega-Net|Compu-Global-Hyper-Mega-Net (CGHMN)]] exists in a difficult kind of space. We aim to emulate "the old web". A time of roughly "1995 to around 2005 or so". A sort of nebulous "Before Web 2.0 took off" kind of period. Though, really we support anything that speaks ethernet and (usually) TCP/IP. We've had devices as old as a DOS 286 PC clone connected successfully. Most users trend toward Windows XP as their platform of choice due to its relative flexibility and widespread hardware and software support


Unfortunately for all of us we live at the "[[wikipedia:End_of_history|end of history]]". In 1995 the "World Wide Web" was in its infancy in such a way that every single year brought quantum technological leaps over the previous year. By the end of the millennium we'd gone from rudimentary analog Dial-Up services to ''Wireless Networking'' being accessible to consumers (Apple's AirPort routers alone showed up in 1999)

However on a technical level this began to create severe issues. The internet as it was originally designed assumed simple "end-to-end" connectivity. Every computer on the internet could (more or less) talk to another computer without exception.


&lt;big&gt;'''This created two major problems:'''&lt;/big&gt;

The first one was IP exhaustion. Even by the 1990's there was an understanding that there simply wouldn't be enough IP addresses for everyone on the internet. This needed to be fixed, and fast! This lead to IPv6 as an evolutionary upgrade (a problem the internet still struggles to even deploy in 2025, despite being ratified in 1998)


The second, and much more obvious problem was security. By the year 2000 it was obviously apparent that every machine being able to talk to every other machine on Earth was a problem. Particularly when the dominant operating system these machines ran was what could be charitably described as..."not great" in terms of security. In the 2000's this would only escalate as the "[[wikipedia:ILOVEYOU|ILOVEYOU]]" worm gave way to some of Windows XP's greatest hits, [[wikipedia:Blaster_(computer_worm)|Blaster]], [[wikipedia:Sasser_(computer_worm)|Sasser]], [[wikipedia:Mydoom|Mydoom]], [[wikipedia:Nimda|Nimda]] and [[wikipedia:Conficker|Conficker]]. Among others. 

A remedy proposed in the 1990's to the issue of IP exhaustion was "Network Address Translation" or "NAT". In layman terms this allows a bunch of computers to all sit behind a single IP address using a device such as a router. This technology is so ubiquitous that even in 2025 at time of writing it's still the defacto standard for home and business computers and other devices to access the modern internet.  

'''''However,''''' this technology came at a cost. The internet as most folks imagine (or remember it) was originally built on the idea that every computer had its own, unique, IP address. NAT broke that assumption. And, in doing so, programs broke. Sometimes completely with services like FTP, sometimes in subtle ways. Like being unable to connect certain game players in a StarCraft lobby. 


The problem that NAT introduced was that while "outbound" traffic would work fine. Such as you connecting to a website. If a program needed to ''receive'' data on your local computer, it could no longer simply sit and wait for a connection from a remote PC. An example would be AOL Instant Messenger (AIM). Chats between users are routed through a remote server. You and the Other User talk to a central server and it handles sending messages to-and-fro. ''However'' to save on bandwidth, sending files happens directly between users. If either user is behind NAT. They won't be able to "see" the remote computer and send data to it as desired.

The "solution" to this problem is known as '''''Port Forwarding'''''. You tell your router that [these ports] *always* go to [this IP address on the LAN] exclusively. This (mostly) solved the problem at the time. Additional solutions were proposed such as "UPnP" to allow programs to ask the router to forward ports for them dynamically. However, support for this was few-and-far-between (mostly BitTorrent clients) and in time it faded into oblivion. 


As stated before, we live at the end of history. Which means we have the benefit of looking back on what was, and understanding the flaws. Which (finally) brings us to the point of this wiki page. 

=== Okay but what does that have to do with CGHMN? ===
Every CGHMN user is allocated a /24 block of IP's. Effectively every user has 253 IP addresses to use as they'd like. This was a deliberate decision both to maximize the amount of freedom users would have to connect ALL their retro equipment if desired, and to try and allow direct end-to-end connectivity that the old web "expects"

'''''However''''' because we have the benefit of historical hindsight. Having directly allocated IP addresses does not mean that your devices are directly exposed to the network. By default (if using OpenWRT with Snep's setup script) your IP block will be ''firewalled'' against incoming connections. This is a necessary security measure because because of the very nature of "running a retro network". Connecting machines that are (likely) un-patched would make them immediately vulnerable to attack. Even before they're properly configured for service by the end user.

=== So, what stuff breaks, exactly? ===

There's no definitive list of "what" breaks under this decision. A broad (but by no means encompassing) list of things that ''won't work'' are

- Servers. You won't be able to run any kind of server or service (EG: hosting your own website, running a game server) without the ability for users to connect to it

- Games that '''''don't''''' use a server browser. Games like Quake or Halo where users all connect to a single server to play on will work (provided the server is either port forwarded or the firewall is disabled) but other games such as StarCraft or Command &amp; Conquer have players connect dynamically connect to a single player as the "host" (typically the player that created the game lobby). These will not work

- FTP! FTP is such an old protocol that the '''''remote server''''' initiates a connection back to the client and then begins sending files that way. This was fixed in [https://datatracker.ietf.org/doc/html/rfc1579 RFC 1579] with the "Firewall-Friendly FTP" proposal. Unfortunately despite being proposed in February 1994, some software such as Microsoft FrontPage did not enable it until 2003(!)

- AIM file transfers. As described already on this wiki page, AIM (and IRC and other chat clients such as MSN or Yahoo) all use a direct connection between two computers to send files across a network


=== How do I opt-out out? ===
&lt;br&gt;

&lt;br&gt;

&lt;big&gt;'''It should be made completely clear that opting out of using the OpenWRT firewall is not a decision that should be made lightly. We cannot explicitly guarantee that a user won't accidentally (or intentionally) release a malware Pandora's Box on the network. Blaster/Sasser/Mydoom/ILOVEYOU/etc are still real malware samples that can be downloaded and executed either by mistake or by a malicious user. We highly recommend installing any and all software patches that were (or are) available for your chosen systems before doing this!'''&lt;/big&gt;

There are two "modes" of opt-out available. Depending on user preference. 

The most drastic is simply to disable OpenWRT's firewall completely. This means any machine you plug in will have direct access to the network and any other devices on the network will be able to directly access it. If you choose this option we highly recommend putting any machines behind a (preferably modern!) Firewall and then port forwarding as necessary 

The other option is to set a static (fixed) IP address on the device you want to run servers or play games from. Once this is done you can access the OpenWRT Firewall page (Network -&gt; Firewall) and manually forward the required ports for that specific host.</text>
    <sha1>c40314fc94117a747b1195d0f2b436dc63130c38</sha1>
  </revision>
  <revision>
    <id>299</id>
    <parentid>298</parentid>
    <timestamp>2025-10-27T12:30:06Z</timestamp>
    <contributor>
      <username>Snep</username>
      <id>5</id>
    </contributor>
    <minor/>
    <comment>Small adjustment in the last sentence on how to allow inbound ports for clearer instructions on where to set up the rules</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8092" xml:space="preserve">=== A brief history on how the internet worked in the 1990's ===

[[Compu-Global-Hyper-Mega-Net|Compu-Global-Hyper-Mega-Net (CGHMN)]] exists in a difficult kind of space. We aim to emulate "the old web". A time of roughly "1995 to around 2005 or so". A sort of nebulous "Before Web 2.0 took off" kind of period. Though, really we support anything that speaks ethernet and (usually) TCP/IP. We've had devices as old as a DOS 286 PC clone connected successfully. Most users trend toward Windows XP as their platform of choice due to its relative flexibility and widespread hardware and software support


Unfortunately for all of us we live at the "[[wikipedia:End_of_history|end of history]]". In 1995 the "World Wide Web" was in its infancy in such a way that every single year brought quantum technological leaps over the previous year. By the end of the millennium we'd gone from rudimentary analog Dial-Up services to ''Wireless Networking'' being accessible to consumers (Apple's AirPort routers alone showed up in 1999)

However on a technical level this began to create severe issues. The internet as it was originally designed assumed simple "end-to-end" connectivity. Every computer on the internet could (more or less) talk to another computer without exception.


&lt;big&gt;'''This created two major problems:'''&lt;/big&gt;

The first one was IP exhaustion. Even by the 1990's there was an understanding that there simply wouldn't be enough IP addresses for everyone on the internet. This needed to be fixed, and fast! This lead to IPv6 as an evolutionary upgrade (a problem the internet still struggles to even deploy in 2025, despite being ratified in 1998)


The second, and much more obvious problem was security. By the year 2000 it was obviously apparent that every machine being able to talk to every other machine on Earth was a problem. Particularly when the dominant operating system these machines ran was what could be charitably described as..."not great" in terms of security. In the 2000's this would only escalate as the "[[wikipedia:ILOVEYOU|ILOVEYOU]]" worm gave way to some of Windows XP's greatest hits, [[wikipedia:Blaster_(computer_worm)|Blaster]], [[wikipedia:Sasser_(computer_worm)|Sasser]], [[wikipedia:Mydoom|Mydoom]], [[wikipedia:Nimda|Nimda]] and [[wikipedia:Conficker|Conficker]]. Among others. 

A remedy proposed in the 1990's to the issue of IP exhaustion was "Network Address Translation" or "NAT". In layman terms this allows a bunch of computers to all sit behind a single IP address using a device such as a router. This technology is so ubiquitous that even in 2025 at time of writing it's still the defacto standard for home and business computers and other devices to access the modern internet.  

'''''However,''''' this technology came at a cost. The internet as most folks imagine (or remember it) was originally built on the idea that every computer had its own, unique, IP address. NAT broke that assumption. And, in doing so, programs broke. Sometimes completely with services like FTP, sometimes in subtle ways. Like being unable to connect certain game players in a StarCraft lobby. 


The problem that NAT introduced was that while "outbound" traffic would work fine. Such as you connecting to a website. If a program needed to ''receive'' data on your local computer, it could no longer simply sit and wait for a connection from a remote PC. An example would be AOL Instant Messenger (AIM). Chats between users are routed through a remote server. You and the Other User talk to a central server and it handles sending messages to-and-fro. ''However'' to save on bandwidth, sending files happens directly between users. If either user is behind NAT. They won't be able to "see" the remote computer and send data to it as desired.

The "solution" to this problem is known as '''''Port Forwarding'''''. You tell your router that [these ports] *always* go to [this IP address on the LAN] exclusively. This (mostly) solved the problem at the time. Additional solutions were proposed such as "UPnP" to allow programs to ask the router to forward ports for them dynamically. However, support for this was few-and-far-between (mostly BitTorrent clients) and in time it faded into oblivion. 


As stated before, we live at the end of history. Which means we have the benefit of looking back on what was, and understanding the flaws. Which (finally) brings us to the point of this wiki page. 

=== Okay but what does that have to do with CGHMN? ===
Every CGHMN user is allocated a /24 block of IP's. Effectively every user has 253 IP addresses to use as they'd like. This was a deliberate decision both to maximize the amount of freedom users would have to connect ALL their retro equipment if desired, and to try and allow direct end-to-end connectivity that the old web "expects"

'''''However''''' because we have the benefit of historical hindsight. Having directly allocated IP addresses does not mean that your devices are directly exposed to the network. By default (if using OpenWRT with Snep's setup script) your IP block will be ''firewalled'' against incoming connections. This is a necessary security measure because because of the very nature of "running a retro network". Connecting machines that are (likely) un-patched would make them immediately vulnerable to attack. Even before they're properly configured for service by the end user.

=== So, what stuff breaks, exactly? ===

There's no definitive list of "what" breaks under this decision. A broad (but by no means encompassing) list of things that ''won't work'' are

- Servers. You won't be able to run any kind of server or service (EG: hosting your own website, running a game server) without the ability for users to connect to it

- Games that '''''don't''''' use a server browser. Games like Quake or Halo where users all connect to a single server to play on will work (provided the server is either port forwarded or the firewall is disabled) but other games such as StarCraft or Command &amp; Conquer have players connect dynamically connect to a single player as the "host" (typically the player that created the game lobby). These will not work

- FTP! FTP is such an old protocol that the '''''remote server''''' initiates a connection back to the client and then begins sending files that way. This was fixed in [https://datatracker.ietf.org/doc/html/rfc1579 RFC 1579] with the "Firewall-Friendly FTP" proposal. Unfortunately despite being proposed in February 1994, some software such as Microsoft FrontPage did not enable it until 2003(!)

- AIM file transfers. As described already on this wiki page, AIM (and IRC and other chat clients such as MSN or Yahoo) all use a direct connection between two computers to send files across a network


=== How do I opt-out out? ===
&lt;br&gt;

&lt;br&gt;

&lt;big&gt;'''It should be made completely clear that opting out of using the OpenWRT firewall is not a decision that should be made lightly. We cannot explicitly guarantee that a user won't accidentally (or intentionally) release a malware Pandora's Box on the network. Blaster/Sasser/Mydoom/ILOVEYOU/etc are still real malware samples that can be downloaded and executed either by mistake or by a malicious user. We highly recommend installing any and all software patches that were (or are) available for your chosen systems before doing this!'''&lt;/big&gt;

There are two "modes" of opt-out available. Depending on user preference. 

The most drastic is simply to disable OpenWRT's firewall completely. This means any machine you plug in will have direct access to the network and any other devices on the network will be able to directly access it. If you choose this option we highly recommend putting any machines behind a (preferably modern!) Firewall and then port forwarding as necessary 

The other option is to set a static (fixed) IP address on the device you want to run servers or play games from. Once this is done you can access the OpenWRT Firewall page (Network -&gt; Firewall -&gt; Traffic Rules) and manually allow the required ports for that specific host to pass the firewall.</text>
    <sha1>009093b444359470ea5233826202950339350d6a</sha1>
  </revision>
</page>
</mediawiki>